Hi, When using maven 2, you have to stick to a pretty standard lifecycle (of course, you could change it, but that wouldn't be a good idea).
What you generally do is bind an ant target to a lifecycle phase. So for example, you can bind your goal1 ant target to the generate-source phase, and your goal2 ant target to the package phase (or whatever, depending on what your goals are). And Maven will make sure everything has been going fine until the package phase, including your goal1 ant target. So, to sum it up, there is no general answer to your question. It depends.... But most of the time, maven 2 solution is far simpler that what you're trying to maintain in your maven1/ant targets. Be sure to read the M2 FAQ for Maven 1 users: http://maven.apache.org/maven1.html Denis hibikijoji wrote: > > To all, > > I am currently migrating from the Maven 1 to the Maven 2 build system. > Here's the scenario: > > In maven 1, I have goals in maven.xml that has a prereq attribute. For > argument's sake, let's say its: > > <goal name="foo:bar" > prereqs="clean, goal1, goal2"> > <!-- insert some ant script code here --> > </goal> > > If goal1 is specified within the plugin whereas goal2 isnt, What is the > equivalent in implementing this in maven 2? > > > > -- View this message in context: http://www.nabble.com/-m2--Calling-goals-outside-a-plugin-tf1970783.html#a5417037 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
