I'm trying to figure out if it is even possible to override a plugin's default phase/goal associations. I'm basically working on a war project. What I'd ultimately like to do is change what maven-war-plugin's goals are called during the package lifecycle under different profiles. Without a profile specified, I want to do a war:inplace because we have tomcat installed locally. Under the env-qa profile, I'd like the package lifecycle to do a war:war (and then additionally call tomcat:redeploy, but it's beyond the scope of my current question).
When I look inside the maven-war-plugin.jar's plugin.xml file I see that it binds both it's war:exploded and war:war goals to the package lifecycle. I'd like to turn that off. Is it possible? Also, for additional consideration, do I need to do something different if I put this into a parent pom shared by multiple projects? Thanks for any help or pointers you could provide. Greg Vaughn [EMAIL PROTECTED] ====================================================================== Confidentiality Notice: The information contained in and transmitted with this communication is strictly confidential, is intended only for the use of the intended recipient, and is the property of Countrywide Financial Corporation or its affiliates and subsidiaries. If you are not the intended recipient, you are hereby notified that any use of the information contained in or transmitted with the communication or dissemination, distribution, or copying of this communication is strictly prohibited by law. If you have received this communication in error, please immediately return this communication to the sender and delete the original message and any copy of it in your possession. ======================================================================
