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 causes the error. Marcel On Thu, Feb 25, 2021 at 1:28 PM Ben Weidig <b...@netzgut.net> wrote: > 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 migration tool available, and the necessary steps are in the > release notes > > https://tapestry.apache.org/release-notes-570.html > > Hope this helps! > Ben > > On Thu, Feb 25, 2021 at 9:03 AM Marcel Schepers <marcel.schep...@gmail.com > > > wrote: > > > Hello, > > After upgrading to 5.7.0 I get this error message when trying to run my > > development version using Jetty's Maven plugin: > > > > java.lang.NoClassDefFoundError: org/apache/tapestry5/ioc/Configuration > > > > Any ideas what needs to be added to what classpath? > > > > Best, > > Marcel > > >
