Using custom extension you can setup a custom lifecycle for JS project with a predefined set of plugins. We should also consider mixins (maven 3.1) that may make such things easier in near future.
merging jstools to mojo using a iterative approach could be the simpliest path : add the jstools mojos as is to SVN and just refactor the packages names. Then see how we could merge some goals, deprecate other, keep both of them if valueable, etc... 2010/10/26 Manos Batsis <[email protected]> > On 10/26/2010 02:00 PM, nicolas de loof wrote: > >> As you noticed, the mojo "js plugin" should be splitted into mulitple >> plugins for various ways to build / use JS. I also don't thing an >> all-in-one plugin is the best way for JavaScript. Maybe using >> javascript-maven-tools as an umbrella plugin, define a sub-groupId >> org.codehaus.mojo.javascript and have dedicated plugins for various JS >> tools could make things cleaner. >> > > Suppose we through the jstools into the mix, would it be possible to allow > both multiple plugins and a bundle plugin that extends/depends-on the > plugins individual plugins? > > Cheers, > > Manos > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
