if they are going to be building your project, they need to install maven, and such so they will need to have at least some awareness of maven.
But I would instead have a plugin installation mechanism and get the users to install the plugins into a standard deployed web-app, e.g. how hudson works On 9 December 2010 11:15, kdannies <[email protected]> wrote: > > Hi! > > I'm developing in a war-project. This war project have some plugins. For > different purposes i do need different plugin sets. Of course, it's easy > just to add or remove the plugins as dependency in the POM of the main > project, but I'm supposed to do this in an easier way like a config file so > users of my project, not aware of maven, can build their project with a > specified plugin set on your own. > > Are their any suggestions to realize this? > > Best regards > Kai Dannies > -- > View this message in context: > http://maven.40175.n5.nabble.com/Optional-Plugins-in-War-project-tp3298747p3298747.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
