It certainly should not run twice. It should run all the goals in the packaging mojo and then add on the additional goals after packaging but not run them again. I am not seeing that behavour so i will have to investigate the scenario you are describing. I have a number of mojos that run during the packaging phase and i am not seeing it run multple times. I will try to look into it but if you have suggestions i am more than happy to make changes to the mojo.
Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -----Original Message----- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Thursday, November 16, 2006 4:13 AM To: [email protected] Subject: Execute phase in weblogic:appc I've doubts in weblogic-maven-plugin's appc mojo. The <executePhase> in the plugin.xml is 'package' which means that it will bounded to the pom along with other goals with 'package' phase. According to the write up at http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.ht ml, when the appc mojo will execute the tasks already executed in the package phase and the preceding phases will rerun. I've appc in an pom with 'ear' packaging. The ear plugin has the following life-cycle, http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html#ear So when appc is executed it will again generate the application.xml and the ear . Also i've a antrun plugin defined to in the 'package' phase that generates webservices using the generated ear. The whole life cycle executing twice is adding a considerable amount of time to the build process. Is there a way to avoid this? Moving the appc to install phase will install the ear to the repository first and run appc on the ear in the build directory. Which is not desirable. Any thoughts??? -- View this message in context: http://www.nabble.com/Execute-phase-in-weblogic%3Aappc-tf2642288s177.html#a7 375755 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
