actually looks like this will work (but not perfect):

1) run 'mvn clean install' for parent POM
2) run 'mvn war:exploded' for EAR module
3) rename WAR directory (as required)
4) delete package WAR in EAR directory
5) copy exploded WAR directory (from #3) to EAR directory
6) copy to app server deploy directory

The problem is that the WAR is unnecessarily being packaged via war:war goal
during 'mvn clean install' (assuming during package phase).

Is it possible to replace the war:war goal invocation during the package
lifecycle phase with war:exploded instead?

Or must you invoke all the goals one a time at the command line instead of a
simple 'mvn clean install'?

This is one area where Ant is much more flexible than Maven (or at least
it's easier to customize invocations of targets in Ant than it is with goals
in Maven's lifecycle phases)...
-- 
View this message in context: 
http://maven.40175.n5.nabble.com/Maven-3-explode-goal-tp946368p946383.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to