Re: Package org.w3c.dom can prevent compilation with java 14

Thanks for pointing that out.

The uber-JAR approach shows its limitations here. The 2.7.2 edition 
offers a slim JAR so you can manage your own dependencies in a civilised 
way. This is the way forward, I think, and AFAIK correctly done.

Jeff Allen

On 23/12/2020 23:12, Nicolas Falliere wrote:
> Just an FYI, something I noticed when migrating a code base from jdk 
> 11 to 14.
>
> If a project using classes in org.w3c.dom is in the unnamed module, 
> javac will report a conflict since org.w3c.dom is accessible from both 
> <unnamed> and java.xml modules.
>
> A solution is to manually remove org.w3c.dom from the jython-xxx.jar.
>
> Best regards,
> --
> Nicolas Falliere ([email protected] <mailto:[email protected]>)
> JEB Decompiler, Founder and Architect
> PNF Software <https://www.pnfsoftware.com/>| Follow us on Twitter 
> <https://twitter.com/jebdec> | Join us on Slack 
> <https://www.pnfsoftware.com/chat> | Bulletin Board 
> <https://www.pnfsoftware.com/forum>
>

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev