If you want to enable Workspace Resolution with m2eclipse, you also may want to look into the <extraClasspath> configuration item in the maven jetty plugin. (<plugin><configuration><webAppConfig><extraClasspath>...)
M2eclipse lets you see the module's classes while you work, and the extraClasspath entry lets Jetty see them without having to repeatedly mvn install your module. So, you would have something like <extraClasspath>../module1/target/classes,../module2/target/classes</extraClasspath> I find this can get a bit finnicky at times, but it can save time when a module is undergoing lots of changes. On Mon, Jan 28, 2013 at 2:48 PM, Peter Wendorff <wendo...@uni-paderborn.de> wrote: > Hi. > I tried to setup a modular tapestry application with Maven and Eclipse. > Creating the core application with maven is easy and works. > Creating a java project with a Manifest file that exports some packages I > easy, but how do I get the core application to find/load the module using > run Jetty? > How/Where do I have to set the dependencies? > Is there a sample project setup for that use case? (modular tapestry > application in eclipse using jetty as (debug) container) > > regards > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Jonathan Barker ITStrategic --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
