-
-
Notifications
You must be signed in to change notification settings - Fork 901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test against upstream htmlunit-neko #2565
Comments
Well, this is a bummer: htmlunit-neko dropped compatibility with Xerces in 2.68.0 (see HtmlUnit/htmlunit-neko#17 for some context), which means 2.67.0 is the latest version we can compile against without some work. I've spiked a bit today on what's involved, and it's mostly refactoring the XML and HTML4 parser context java classes to not inherit from one another. I think I can do it with a little bit more work. |
Yust released version 3.1.0 of Neko. Feel free to contact me if i you need some support with updating. |
Would be fantastic to see some progress here, as nokogiri-java reports a vulnerability via |
@chadlwilson If you've got time and the motivation, please take a look at the WIP branch at #2856. I need help! |
For what it's worth (and for anyone else who arrives here concerned about CVEs being reported against nokogiri java variant) the current CVEs reported against neko-htmlunit My personal assessment is here alongside a discussion of why it's not so appropriate to blanket suppress these within tools such as OWASP Dependency Check: jeremylong/DependencyCheck#5656 (comment) |
Closing this because it feels like a bigger investment of time than I'm willing to make right now. However, if someone from the JRuby community wants to take this on I'd be happy to consult/support/help in any way I can. |
I recently shipped a PR upstream: HtmlUnit/htmlunit-neko#13
If that gets accepted, then the pending tests from 7cec00e and 277db2e should start passing, and that's a good time to implement upstream testing against https://github.com/HtmlUnit/htmlunit-neko/
The text was updated successfully, but these errors were encountered: