On 9 March 2010 18:43, Alan D. Cabrera <[email protected]> wrote: > My understanding is that there is a technical veto on this change. More > specifically the proper name of the plugin should be eba-maven-plugin and > *not* maven-eba-plugin.
Are you saying that you veto this change? If so could you justify why you think it should be eba-maven-plugin and not maven-eba-plugin. We have maven-bundle-plugin, maven-jar-plugin, maven-zip-plugin and maven-assembly-plugin for collecting files up into an archive. An eba is an archive too and calling it maven-eba-plugin would seem to exactly follow the precedent already set. I'm sure you must have a reason, but I'm missing it right now. Cheers, Jeremy > > > Regards, > Alan > > > On Mar 9, 2010, at 8:11 AM, Jeremy Hughes wrote: > >> Graham just renamed the plugin to fall in line with other plugins. So >> it is no longer called eba-maven-plugin. There is a snapshot of the >> plugin deployed to the snapshot repo so it should be picked up. >> However, you can work around this by first building the parent top >> level module then build the maven-eba-plugin module. Then you can go >> back to the top level and build everything. >> >> Cheers, >> Jeremy >> >> On 9 March 2010 15:33, David Bosschaert <[email protected]> >> wrote: >>> >>> I just created a fresh new Aries checkout today but it fails to build: >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] BUILD ERROR >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] The plugin 'org.apache.aries:maven-eba-plugin' does not exist or >>> no valid >>> version could be found >>> >>> I also see that Hudson's been red for a number of days: >>> http://hudson.zones.apache.org/hudson/view/Aries/ >>> >>> Whats going on? >>> >>> David >>> > >
