I think forked lifecycles are often "too helpful," like Clippy the Paperclip. If you can't find a real solution, you could patch the plugin. Give it a new Mojo that just calls the original, and put different annotations on the new mojo so it doesn't fork a lifecycle. That seems to be roughly how the assembly plugin provides both assembly:assembly and assembly:attached.
Paul Dmystery wrote: > > 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.html, > 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#a7380573 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
