I'm sorry, I'm sorry my fault!
A forgotten dependency in one of my Maven modules.
Works like a charm now.
Marcel
On Thu, Feb 25, 2021 at 4:21 PM Ben Weidig wrote:
> Ah ok. I don't know much about maven and jetty:run, we run an embedded
> jetty as Java application, and use gradle ;-)
>
>
Ah ok. I don't know much about maven and jetty:run, we run an embedded
jetty as Java application, and use gradle ;-)
It kinda sounds like a (transitive) dependency issue.
Something still wants 5.6.x and is trying to load a class from the old
package.
Maybe "mvn dependency:tree -Dverbose" can shed
Hello Ben,
Thank you very much for your assistance.
What is was trying to say is that the Maven/Jetty occurs after the
migration process as described in the release notes. As far as I can see
the migration tool did its job as the project compiles error free. It is
the 'mvn jetty:run' command that
Hi Marcel,
Tapestry 5.7.0 is not a simple drop-in upgrade from 5.6.x and needs manual
migration steps.
A lot of classes, like Configuration, moved to new packages, to make the
Java 9+ module system (partially) possible, and decouple the UI-related
parts from the general web-stack.
There's a migra
