rbri
commented
3 months ago Can we use this codelibs fork of nekohtml itself instead of htmlunit-neko as codelibs also seems to be a working fork without any major vulnerabilities.
Yes you can!
Problem is htmlunit-neko seems to use it's own version of xerces2j jar instead of xercesImpl. But xerces2j of htmlunit-neko doesn't seem to be actively maintained & couldn't find any Maven link to download xerces2j jar as well.
Maybe the text on the home page is a bit misleading - htmlunit-neko uses a fork of xerces BUT all the forked code is now part of the neko-htmlunit.jar. neko-htmlunit.jar has no dependencies at all (at runtime). Therefore you do not have to search for a xerces / xml-api dependency.
Hope that helps....
LogeswaranRamasamy
@rbri Can we use this codelibs fork of nekohtml itself instead of htmlunit-neko as codelibs also seems to be a working fork without any major vulnerabilities. Else is codelibs.nekohtml project not being maintained & should we switch to htmlunit-neko.
Problem is htmlunit-neko seems to use it's own version of xerces2j jar instead of xercesImpl. But xerces2j of htmlunit-neko doesn't seem to be actively maintained & couldn't find any Maven link to download xerces2j jar as well.
Kindly pls advice on this.