On Fri, Nov 8, 2019 at 8:03 PM Charles Roth <cr...@thedance.net> wrote:
Hello! Thanks for announcing the Tapestry 5.5 beta, with Java 9+ support. > Our pleasure! One nitpick: it has support for Java 9, 10 and 11 bytecode. Tapestry itself wasn't modularized yet. > 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 > Did you try making modules out of Tapestry JARs? I'd guess that wouldn't work. > ...which suggests that the Tapestry jars may have 'split packages', i.e. > the same package name in different jars. > Yes, this is a situation which happens now and will need to be addressed when Tapestry itself is modularized. > 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: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
