I asked the same question here: http://tapestry.1045711.n5.nabble.com/Eclipse-Can-run-against-maven-jar-can-t-run-against-local-project-td5714087.html
When running against a project in eclipse, you are running against .class files on the classpath, not a jar file. So tapestry can't see the manifest file(s) and can't auto-load the extra AppModules. I solve this by setting a system property on my run-jetty-run launcher eg: -Dtapestry.modules=foo.bar.ModuleA,foo.bar.ModuleB This can also be solved by using the @SubModule annotation in your webapp's AppModule. Don't worry, in production it won't include them twice. I don't really like this approach as it defeats the purpose of the manifest. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Modular-Tapestry-application-in-Eclipse-tp5719628p5719634.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
