On 04/04/2011 12:08 PM, Wayne Fay wrote:
The answer is : mvn prepare-packagewar:exploded
Thanks Asmann for your instruction :x
It took 5 emails to figure out that you really just wanted an exploded
war to deploy to an App Server during testing.
In the future, instead of asking someone to help you implement the
solution you've imagined, you should just tell the list what problem
you are trying to solve, and then let someone tell you the right
solution to implement.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Best advice this month!!!
Should be a requirement for all new users to prefix their first question
with a standard preamble:
Development target: standalone app, webapp under [tomcat, jboss,
websphere, ....], applet,plug-in....
Language:
Maven Version:
Development IDE: Eclipse, Netbeans,
CI server: Hudson,...., none
Maven Repo: Nexus, Artifactory, none (My advice if, none, get one
and come back if you still have a problem)
Project team size: x people
Number of deliverable artifacts: x
Overall goal: (trying to set up a release strategy, etc., etc.,)
Specific task and problem: Want to get Maven to automatically decide
when to make a new release version. Maven never seems to be able to
figure out when my code is working to spec.
Probably not a bad thing for the second and subsequent post as well.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
