Thank you!
On 10/3/2020 4:29 PM, Thiago H. de Paula Figueiredo wrote:
Hello, Charles!
TAP5-2641 is taking care of fixing the split packages problem, plus setting
automatic module names for all the Tapestry JARs ("org.apache.tapestry" +
project name, except for tapestry5-annotations, which will
Hello, Charles!
TAP5-2641 is taking care of fixing the split packages problem, plus setting
automatic module names for all the Tapestry JARs ("org.apache.tapestry" +
project name, except for tapestry5-annotations, which will be
org.apache.tapestry-annotations'). Lots of classes needed to be moved
On Tue, Nov 12, 2019 at 8:36 PM Charles Roth 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 succe
Hmm, thanks for the quick response.
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
On Fri, Nov 8, 2019 at 8:03 PM Charles Roth 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) suc
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 u
