Yes, using our shared repository would be another option. We would have to maintain the plugin as if it were more like a 3rd party resource rather than part of the product's source, but maybe that's the right way to think about. Not sure, but if it works, I think that's fine. Thanks for the help.
On Mon, Jan 31, 2011 at 12:25 PM, Hilco Wijbenga <[email protected]>wrote: > On 31 January 2011 10:08, E S <[email protected]> wrote: > > 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. > > How would any of this affect your build server or new developers? Just > deploy the plugin once and it's available to everyone. > > You do have a place to deploy artifacts, right? If you don't then I > would strongly suggest you set that up ASAP. (It's pretty simple.) I > think you'll find that Maven doesn't scale very well without it so > you're going to need it eventually anyway. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
