2012/7/1 Thomas Broyer <[email protected]>: > Hi all, > > Let's say I have a mojo that requires both a phase (process-classes) > and a goal (war:exploded) to be executed before it itself is run, am I > right to think that I should create a new custom lifecycle that binds > the war:exploded goal to some phase after process-classes, copying the > previous phases from the war packaging lifecycle and declaring > @execute phase=some-phase lifecycle=my-lifecycle? Correct that should work. > > I found out about the mojo-executor project; would it be wise to use > it instead? (declare @execute phase=process-classes and then use the > mojo-executor component to run the war:exploded goal)
Long time ago I checked and that didn't work with mvn3 (maybe now it's fixed: frankly no idea on that) > > Am I on the right track? What would be the best practice? Perso I would use the lifecycle approach which is more IMFO in the maven supported approach. > > -- > Thomas Broyer > /tɔ.ma.bʁwa.je/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
