Drink the Maven Kool-aid. You are fighting the Maven way, that is usually a sign that you are doing something that you really do not want to do (but you just have not realised it yet)
Perhaps if you told us what plugin-x and plugin-y do we can help... Also, sometimes the solution is to split your module into separate modules. Also, what you want to do is add the executions to the phase named after their function. So, if you are generating source code, or processing source code, you would attach the plugin executions to the generate-sources or process-sources phase respectively -Stephen 2009/11/11 boraldo <[email protected]>: > >>> you need to put the executions in different phases if they need a > defined order > I don't want that phases to execute. For example clean will clean, compile > wil compile. If there any phases besides initialize that do nothing ? > > Stephen Connolly-2 wrote: >> >> not the bug you think it is >> >> you need to put the executions in different phases if they need a >> defined order >> >> the bug is allowing you to list the same plugin twice in the one >> plugins section >> >> Sent from my [rhymes with tryPod] ;-) >> >> On 10 Nov 2009, at 17:51, Paul Benedict <[email protected]> wrote: >> >>> This is probably a bug since the order of plugins should be respected. >>> >>> Have you checked the ticket list of 2.2.2 or 3.0-alpha-3 to see if it >>> is already fixed? >>> >>> And are you running 2.2.1? >>> >>> Paul >>> >>> On Tue, Nov 10, 2009 at 11:48 AM, boraldo <[email protected]> wrote: >>>> >>>> Suppose I have to execute some actions after some phase. >>>> These actions are made plugins X and Y. >>>> 1st action - executed by plugin X >>>> 2nd action - executed by plugin Y >>>> 3rd action - executed by plugin X >>>> >>>> I wrote the following pom: >>>> >>>> <build> >>>> <plugins> >>>> <plugin> >>>> <artifactId>plugin-x</artifactId> >>>> <executions> >>>> <execution> >>>> <id>step-1-x</id> >>>> <phase>initialize</phase> >>>> <goals> >>>> <goal>goal-x-1</goal> >>>> </goals> >>>> </execution> >>>> </executions> >>>> </plugin> >>>> <plugin> >>>> <artifactId>plugin-y</artifactId> >>>> <executions> >>>> <execution> >>>> <id>step-2-y</id> >>>> <phase>initialize</phase> >>>> <goals> >>>> <goal>goal-y-1</goal> >>>> </goals> >>>> </execution> >>>> </executions> >>>> </plugin> >>>> <plugin> >>>> <artifactId>plugin-x</artifactId> >>>> <executions> >>>> <execution> >>>> <id>step-3-x</id> >>>> <phase>initialize</phase> >>>> <goals> >>>> <goal>goal-x-2</goal> >>>> </goals> >>>> </execution> >>>> </executions> >>>> </plugin> >>>> </plugins> >>>> </build> >>>> >>>> I executed: >>>> mvn initialize >>>> >>>> But the sequence of executions was wrong: >>>> 1. step-1-x >>>> 2. step-3-x >>>> 3. step-2-y >>>> >>>> This means that each plugin executes all its executions, then the >>>> next >>>> plugin starts to work. >>>> Can I corrupt such scenario ? >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/How-can-I-execute-plugin-X%2C-then-plugin-Y%2C-then-plugin-X-again---tp26287350p26287350.html >>>> 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] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- > View this message in context: > http://old.nabble.com/How-can-I-execute-plugin-X%2C-then-plugin-Y%2C-then-plugin-X-again---tp26287350p26298018.html > 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]
