maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From maven apache <>
Subject effective practice for web application development using maven
Date Tue, 12 Mar 2013 07:24:32 GMT
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:


And the app-common/pom.xml:


the app-webapp/pom.xml:


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?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message