[quote=http://maven.apache.org/maven2/lifecycle.html] The second way to add goals to phases is to configure plugins in your project. As you will see in the later sections, plugins contain information that says where to bind particular goals to. Note that adding the plugin on its own is not enough information - you must also specify the goals you want run as part of your build.
The goals that are configured will be added to the goals already bound to the lifecycle from the packaging selected. If more than one goal is bound to a particular phase, the order used is that those from the packaging are executed first, followed by those configured in the POM. Note that you can use the executions element to gain more control over the order of particular goals. [/quote] that was from the plugins section. my interpretation (and observation) is that plugins bound in the pom is executed _after_ the default maven buildcycle plugins are run. but i have no idea on how to use executions to have user specified plugins go first than the default plugins. binding your plugin to the process-sources phase should make your plugin run before the generate-resources. ciao! On 11/4/05, David Sag <[EMAIL PROTECTED]> wrote: > Just to answer my own question, and to help others who are wondering the > same thing, I just tried it and the plugin runs *after* the phase it has > been bound to. > > dave > > > David Sag <[EMAIL PROTECTED]> wrote on 04-11-2005 12:57:08: > > > Hi there, > > > > I want my plugin to run after the process-sources phase, and before the > > generate-resources phase. if i bind it to the process-sources phase > will > > it run after that or before it? > > > > dave > > -- "Programming, an artform that fights back" Anuerin G. Diaz Registered Linux User #246176 Friendly Linux Board @ http://mandrivausers.org/index.php http://capsule.ramfree17.org , when you absolutely have nothing else better to do --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
