From: Jeff A. <ja...@fa...> - 2020-12-26 21:49:50
|
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 (ni...@pn... <mailto:ni...@pn...>) > 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> > |