-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The general pattern we've adopted with Maven 2.0 is that of binding your custom behavior to the appropriate place in an absolute lifecycle, rather than relative to some other plugin's execution. The problem with specifying a pre/postGoal is that the referenced goal is the only one that can ever trigger that custom behavior (ties the build to a concrete goal, rather than an abstract action), and it's impossible to inject new behavior between the two (goal and decorator).
In m2, you should be able to determine in which lifecycle phase the mojo in question executes, and bind your custom plugin to the phase before or after it. I know this will probably bring up more questions than it answers, but I'll let you chew on that for a minute and see what other questions you have, rather than delving into all the ins and outs of lifecycle binding... HTH, john Brill Pappin wrote: | Sorry if this has been covered on the list before (a quick search didn't | turn up anything useful). | | Since the maven.xml file is now gone, how to I set up pre/post goals in M2? | | They are one of the really good features of maven 1.x and I'll really miss | them if I can't use them. | | - Brill Pappin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDVQ1VK3h2CZwO/4URAvVtAKCfO/BU0KCtRugnkH3/fC06aGB2lgCfVLcR RAqSwJRR1ux7/X2Mlb1z338= =V6sL -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
