Tapestry 5.5 beta and Java Modularity

Thanks for announcing the Tapestry 5.5 beta, with Java 9+ support.  
We're experimenting with it now under Java 11 (since only 8 and 11 have 
long-term-support).

We're finding that we must use java modules (module-info.java) in order 
to compile, due to issues with the java.xml packages that we use.  (Long 
story.)

Has anyone done this (i.e., use java modules) successfully with Tapestry 
5.5?  I keep getting errors like:

    error: the unnamed module reads package 
org.apache.tapestry5.internal.beaneditor from both tapestry.core and 
beanmodel

...which suggests that the Tapestry jars may have 'split packages', i.e. 
the same package name in different jars.

We're still learning the ins-and-outs of Java Modularity, so it may 
simply be my confusion.  But any thoughts are most welcome!

One possible (crude) workaround may be to merge the tapestry jars into a 
new (single) jar, and treat that as a single "automatic module".  I'll 
try that if nothing else works, and report back.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]