That's certainly an option, but it doesn't work as well as I would like for our build server or new developers getting their dev environments set up. We could get around it using something like build script on top of maven, but I would prefer a cleaner solution in which maven handles it automatically if possible.
On Mon, Jan 31, 2011 at 12:00 PM, Hilco Wijbenga <[email protected]>wrote: > On 31 January 2011 09:53, E S <[email protected]> wrote: > > Anyway, what’s the best way to go about doing this? If I build the plugin > > separately, then run the entire build, it works fine. How can I get maven > to > > do something like that but without two separate builds? > > Why don't you put it in a separate project? Run mvn install or mvn > deploy once and your plugin is available to all of your projects. No > need to build it again. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
