You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Stuart McCulloch <mc...@gmail.com> on 2013/02/27 22:26:00 UTC
[DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
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
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Ferry Huberts <ma...@hupie.com>.
On 27/02/13 22:26, Stuart McCulloch wrote:
> 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?
>
+1 !
--
Ferry Huberts
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Stuart McCulloch <mc...@gmail.com>.
On 28 Feb 2013, at 07:43, Sahoo wrote:
> Stuart,
>
> I really appreciate all the effort you put in to make this plugin so great. But, I am afraid, I can't support the renaming. It is going to frustrate developers already frustrated with lack of good OSGi tools. maven-bundle-plugin works great and we have many people used it now. The renaming is going to confuse them than doing any good that I can think of. I really don't see why maven has this convention that only plugins hosted by Apache Maven can have names starting maven. Please consider -1 on behalf of GlassFish.
No worries, the reason I started this discussion thread is to get feedback from everyone this might affect. Changing the plugin name would mostly be a courtesy to the Maven team, but perhaps it would be better to postpone this until there's a breaking change in the plugin that meant upgrading wouldn't involve a simple version bump.
> Thanks,
> Sahoo
>
> On Thursday 28 February 2013 02:56 AM, Stuart McCulloch wrote:
>> 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
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Stuart McCulloch <mc...@gmail.com>.
On 28 Feb 2013, at 07:54, Felix Meschberger wrote:
> Hi
>
> Thanks for the heads up and thanks for your work you put into this. This is really appreciated and the also community wise the plugin is really a key in the OSGi tooling.
>
> Having said that I appreciate the desire to align with Maven best practices but I share the same concerns as Sahoo: The Maven Bundle Plugin has a good name in the community and thus should not be changed too quickly and easily.
>
> Also, I don't think it should be renamed to "bnd", after all it is a plugin to build bundles and should IMHO reflect that fact for the benefit of our users. That we use bndlib internally is a good (and the right) thing but it is just that: an implementation detail.
Yes, except we do expose bnd as more than an implementation detail - the instruction format is from bnd, and we direct people to bnd's documentation. That said, the packaging type is 'bundle' so changing the name from 'bundle' to 'bnd' would introduce a disconnect here.
> How about a compromise: Just switch from maven-bundle-plugin to bundle-maven-plugin ? Also: How complex would it be to setup aliases ?
Maven does support relocations, but I'm not sure how this works in practice: http://maven.apache.org/ref/3.0.5/maven-model/maven.html#class_relocation
> Regards
> Felix
>
> Am 28.02.2013 um 08:43 schrieb Sahoo:
>
>> Stuart,
>>
>> I really appreciate all the effort you put in to make this plugin so
>> great. But, I am afraid, I can't support the renaming. It is going to
>> frustrate developers already frustrated with lack of good OSGi tools.
>> maven-bundle-plugin works great and we have many people used it now. The
>> renaming is going to confuse them than doing any good that I can think
>> of. I really don't see why maven has this convention that only plugins
>> hosted by Apache Maven can have names starting maven. Please consider -1
>> on behalf of GlassFish.
>>
>> Thanks,
>> Sahoo
>>
>> On Thursday 28 February 2013 02:56 AM, Stuart McCulloch wrote:
>>> 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
>>
>
>
> --
> Felix Meschberger | Principal Scientist | Adobe
>
>
>
>
>
>
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Tang Yong <ta...@cn.fujitsu.com>.
I agree with the following very much!
>That we use bndlib internally is a good (and the right) thing but it
is >just that: an implementation detail.
Thanks
--Tang
Felix Meschberger wrote:
> Hi
>
> Thanks for the heads up and thanks for your work you put into this. This is really appreciated and the also community wise the plugin is really a key in the OSGi tooling.
>
> Having said that I appreciate the desire to align with Maven best practices but I share the same concerns as Sahoo: The Maven Bundle Plugin has a good name in the community and thus should not be changed too quickly and easily.
>
> Also, I don't think it should be renamed to "bnd", after all it is a plugin to build bundles and should IMHO reflect that fact for the benefit of our users. That we use bndlib internally is a good (and the right) thing but it is just that: an implementation detail.
>
> How about a compromise: Just switch from maven-bundle-plugin to bundle-maven-plugin ? Also: How complex would it be to setup aliases ?
>
> Regards
> Felix
>
> Am 28.02.2013 um 08:43 schrieb Sahoo:
>
>> Stuart,
>>
>> I really appreciate all the effort you put in to make this plugin so
>> great. But, I am afraid, I can't support the renaming. It is going to
>> frustrate developers already frustrated with lack of good OSGi tools.
>> maven-bundle-plugin works great and we have many people used it now. The
>> renaming is going to confuse them than doing any good that I can think
>> of. I really don't see why maven has this convention that only plugins
>> hosted by Apache Maven can have names starting maven. Please consider -1
>> on behalf of GlassFish.
>>
>> Thanks,
>> Sahoo
>>
>> On Thursday 28 February 2013 02:56 AM, Stuart McCulloch wrote:
>>> 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
>
>
> --
> Felix Meschberger | Principal Scientist | Adobe
>
>
>
>
>
>
>
>
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Felix Meschberger <fm...@adobe.com>.
Hi
Thanks for the heads up and thanks for your work you put into this. This is really appreciated and the also community wise the plugin is really a key in the OSGi tooling.
Having said that I appreciate the desire to align with Maven best practices but I share the same concerns as Sahoo: The Maven Bundle Plugin has a good name in the community and thus should not be changed too quickly and easily.
Also, I don't think it should be renamed to "bnd", after all it is a plugin to build bundles and should IMHO reflect that fact for the benefit of our users. That we use bndlib internally is a good (and the right) thing but it is just that: an implementation detail.
How about a compromise: Just switch from maven-bundle-plugin to bundle-maven-plugin ? Also: How complex would it be to setup aliases ?
Regards
Felix
Am 28.02.2013 um 08:43 schrieb Sahoo:
> Stuart,
>
> I really appreciate all the effort you put in to make this plugin so
> great. But, I am afraid, I can't support the renaming. It is going to
> frustrate developers already frustrated with lack of good OSGi tools.
> maven-bundle-plugin works great and we have many people used it now. The
> renaming is going to confuse them than doing any good that I can think
> of. I really don't see why maven has this convention that only plugins
> hosted by Apache Maven can have names starting maven. Please consider -1
> on behalf of GlassFish.
>
> Thanks,
> Sahoo
>
> On Thursday 28 February 2013 02:56 AM, Stuart McCulloch wrote:
>> 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
>
--
Felix Meschberger | Principal Scientist | Adobe
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Sahoo <sa...@oracle.com>.
Stuart,
I really appreciate all the effort you put in to make this plugin so
great. But, I am afraid, I can't support the renaming. It is going to
frustrate developers already frustrated with lack of good OSGi tools.
maven-bundle-plugin works great and we have many people used it now. The
renaming is going to confuse them than doing any good that I can think
of. I really don't see why maven has this convention that only plugins
hosted by Apache Maven can have names starting maven. Please consider -1
on behalf of GlassFish.
Thanks,
Sahoo
On Thursday 28 February 2013 02:56 AM, Stuart McCulloch wrote:
> 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
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Tommaso Teofili <te...@adobe.com>.
+1 (non binding)
Tommaso
On 27/feb/2013, at 23:56, Simone Tripodi wrote:
> +1 (non binding)
>
> looking forward to see the new plugin in action!!!
>
> all the best!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Wed, Feb 27, 2013 at 10:26 PM, Stuart McCulloch <mc...@gmail.com> wrote:
>> 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
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Simone Tripodi <si...@apache.org>.
+1 (non binding)
looking forward to see the new plugin in action!!!
all the best!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Wed, Feb 27, 2013 at 10:26 PM, Stuart McCulloch <mc...@gmail.com> wrote:
> 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
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Tang Yong <ta...@cn.fujitsu.com>.
Hi Stuart,
I am sorry that I select -1.
Fistly, updating into bndlib 2.x is greate, however, the reason of -1 is
that bndlib aims to OSGi bundle's development, and we can imagine that
maven-jar-plugin services for common jar and maven-bundle-plugin
services for osgi bundle, so I think that naming(maven-bundle-plugin) is
good enough for I and other developers(I guess).
So, I think that bndlib's upgrading should not cause re-naming maven
osgi plugin.
Thanks
--Tang
Stuart McCulloch wrote:
> 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
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by "Richard S. Hall" <he...@ungoverned.org>.
Fine by me.
-> richard
On 2/27/13 16:26, Stuart McCulloch wrote:
> 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
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Marcel Offermans <ma...@luminis.nl>.
On Feb 28, 2013, at 13:43 , Stuart McCulloch <mc...@gmail.com> wrote:
> 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/users@maven.apache.org/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.
I would say, our users come first. Renaming the plugin causes them problems for no reason (to them) so let's not do that.
Instead, we could also solve this by donating the plugin to the Apache Maven project.
Greetings, Marcel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Stuart McCulloch <mc...@gmail.com>.
On 28 Feb 2013, at 12:57, Guillaume Sauthier (OW2/GMail) wrote:
> It's not completely related to the naming discussion, but more about the
> relation-ship with maven itself.
> Is it possible (in a more a less near future) to have "bundle" type
> recognized by default by maven ?
> --G
That's an interesting idea - as Marcel mentioned perhaps we could consider donating the maven-bundle-plugin to the Apache Maven project, which would then make it easier (though not a done deal) to add 'bundle' as a core packaging type. This would still involve a change in plugin coordinates (groupId org.apache.felix -> org.apache.maven.plugins) but we could look into adding a relocation in the pom.xml to assist users and if we were able to get the 'bundle' packaging recognized by default then migration would mostly involve removing elements from the pom.xml
I'll start a new thread to discuss the contribution idea - just a reminder that nothing has been decided at this point, I want to get wide enough feedback before starting a vote thread.
> 2013/2/28 Stuart McCulloch <mc...@gmail.com>
>
>> 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/users@maven.apache.org/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 <mc...@gmail.com>
>>> 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: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by "Guillaume Sauthier (OW2/GMail)" <gu...@gmail.com>.
It's not completely related to the naming discussion, but more about the
relation-ship with maven itself.
Is it possible (in a more a less near future) to have "bundle" type
recognized by default by maven ?
--G
2013/2/28 Stuart McCulloch <mc...@gmail.com>
> 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/users@maven.apache.org/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 <mc...@gmail.com>
> > 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: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Stuart McCulloch <mc...@gmail.com>.
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/users@maven.apache.org/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 <mc...@gmail.com>
> 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: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
Re: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
Posted by Stuart McCulloch <mc...@gmail.com>.
On 6 Mar 2013, at 15:15, Andrew Kenney wrote:
> Hi Stuart,
>
> There's an open JIRA issue for the maven bundle plugin that would be very useful to have in the new release.
> https://issues.apache.org/jira/browse/FELIX-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
>
> I did some investigation into using OBR last October, but concluded that it was not very useful if the maven bundle plugin couldn't place my project's dependencies into my OBR repo, along with the project's artifact.
> I've tried to use the proposed setting with the latest plugin, but it didn't work.
> <addDependenciesToRepository>true</addDependenciesToRepository>
>
> Do you think this feature would be possible to add?
>
> In my opinion, OBR has some deficiencies... but if the maven bundle plugin had this capability, it overcomes a majority of OBRs problems. OBR is pretty useless if repository maintenance isn't automated.
I'll take a look as part of the ongoing bug triage - btw, if anyone else is interested in this feature (or any others) you can vote for it on JIRA.
> Thanks for your consideration,
> Andrew
>
> -----Original Message-----
> From: Stuart McCulloch [mailto:mcculls@gmail.com]
> Sent: Wednesday, February 27, 2013 4:26 PM
> To: dev
> Subject: [DISCUSS] rename maven-bundle-plugin to bnd-maven-plugin
>
> 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: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org