2009/5/22 Jason van Zyl <jvan...@sonatype.com> > > On 22-May-09, at 10:46 AM, Stephen Connolly wrote: > > >> Then both goals are bound to the integration-test phase, as I would expect >> >> > I think 2.x is a little lax. It should blow up and tell you that you're > trying to wire the mojo to a phase not specified in the mojo itself. If it > is supposed to flexible wrt where it runs in the lifecycle then no phase > should be specified in the mojo. You're doing something the author of the > mojo did not intend. > > Eh, I would not agree (other than in the case of the failsafe-maven-plugin)
I (as a plugin user) might have a perfectly good reason for re-binding a goal to a different phase... for example I might need to execute something in-between and therefore shift things back a phase... ok so that should be a 2.x problem once 3.x gets the build planning code, but I would still think that Maven should not bomb out just because a plugin user has re-bound the phase from the default phase for a goal... +1 for Maven giving a big fat warning though My €0.02 in any case -Stephen
