On Tue, Nov 12, 2019 at 8:36 PM Charles Roth <cr...@thedance.net> wrote:
> Hmm, thanks for the quick response. > We strive to please! :D > It looks like I will have to try the unpack-all-the-tapestry-jars and > pack-them-into-a-single-jar as an "automatic module", after all. > > I will report back if that is successful. > > (This is partly caused by another conflict in our project, with > javax.xml, that is forcing us to use modules. Many people may be able > to use Tapestry as-is by telling their build process to ignore the > module rules.) > I haven't really worked with Java 9+ modules yet, but couldn't you have the non-modularized Tapestry JARs in the classpath instead of the modulepath? > > On 11/12/2019 5:42 PM, Thiago H. de Paula Figueiredo wrote: > > 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 > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Thiago
