On 28 Feb 2013, at 07:05, fbalicchia wrote:
> I think it is the best choice to follow the naming convention.
> What I do not understand is why plugins can't be hosted by Apache
The Apache Maven team prefer to keep the maven-NNN-plugin naming for plugins
developed and maintained by them (ie. those with groupId
org.apache.maven.plugins) whereas Maven plugins developed by other Apache (or
non-Apache) projects are encouraged to use NNN-maven-plugin naming. The idea is
to help avoid confusion about which plugins are directly supported by Apache
Maven team and which are supported elsewhere:
http://www.mail-archive.com/[email protected]/msg128850.html
While renaming the plugin would be a courtesy to the Apache Maven team, it is
not mandatory if it would cause problems for downstream users - hence this
discussion thread.
HTH
--
Cheers, Stuart
> Thanks
>
> Regards
>
> --Filippo
>
> 2013/2/27 Stuart McCulloch <[email protected]>
> Hi folks,
>
> Now that we've got a 2.x version of bndlib in Maven Central
> (http://search.maven.org/#artifactdetails%7Cbiz.aQute%7Cbndlib%7C2.0.0.20130123-133441%7Cjar
> - same level as shipped in bndtools 2) I'm looking to sort out a new release
> of the maven-bundle-plugin, once I've gone through and triaged the pending
> issues in JIRA.
>
> I also figure that now might be the best time to "fix" the plugin name
> according to Maven guidelines:
> http://maven.apache.org/guides/development/guide-plugin-documentation.html -
> apparently the name "maven-NNN-plugin" is supposed to be reserved for plugins
> hosted by Apache Maven, while plugins hosted elsewhere should use names like
> "NNN-maven-plugin".
>
> So along with the upgrade to bndlib 2.x, I'm proposing to change the plugin
> name to:
>
> bnd-maven-plugin
>
> which both respects the Maven plugin naming convention, and recognises the
> bnd code which is actually doing most of the work.
>
> WDYT?
>
> --
> Cheers, Stuart
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
