On Tue, Mar 12, 2013 at 8:24 AM, maven apache <[email protected]>wrote:
> Hi everyone:
>
> I am using maven3 as my J2EE application build tool.
>
> Now I meet some problem during my development --- I found it is so
> inflexible to do the test or debug in the multiple modules.
>
> For example, I have a parent maven project whose pom.xml is like this:
>
> <modules>
> <module>app-common</module>
> <module>app-webapp</module>
> </modules>
>
> And the app-common/pom.xml:
>
> <package>jar</package>
>
>
> the app-webapp/pom.xml:
>
> <package>war</package>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>app-common</artifactId>
> <version>${project.version}</version>
> </dependency>
> <build>
> <finalName>app</finalName>
> <plugins>
> <plugin>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>maven-jetty-plugin</artifactId>
> <configuration>
> <scanIntervalSeconds>10</scanIntervalSeconds>
> <stopKey>foo</stopKey>
> <stopPort>9999</stopPort>
> </configuration>
> </plugin>
> </plugins>
> </build>
>
> Now,the app-common project hold all the classed for the whole
> application,and the app-webapp is responsible for the presentation.
>
> As you can see I use the jetty to set up the web application.
>
> However, each time I make some change inside the project app-common, the
> jetty can not detect it which means that I have to run the "mvn install"
> under the parent project,and restart the jetty to see the update. This is
> too inflexible.
>
> So I wonder how do you guys do this kind of development?
>
I don't use Jetty for multi-module builds; see
http://jira.codehaus.org/browse/JETTY-1517
The tomcat-maven-plugin (starting with 2.0) works great for multimodule
builds; see
http://tomcat.apache.org/maven-plugin-2.1/run-mojo-features.html#Maven_project_structure
--
Thomas Broyer
/tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
