You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2011/01/13 17:05:58 UTC
Rename karaf features plugin with a more generic name
Hi again :)
Sorry to disturb you again :).
In Karaf tooling, we have the features maven plugin to generate the
features descriptor and copy the resources from the repo.
We begin to see some requirement to new maven goals such as:
- karaf:run to run a Karaf instance from maven
- karaf:dist to create a Karaf distribution
- karaf:branding to create a Karaf branding bundle
- karaf:shell to connect to a Karaf instance remotely and bind the shell
- etc, etc
As you can see, I voluntarily define several goals of the same maven plugin.
I propose to refactore the existing features maven plugin by renaming it
with a more generic naming.
For instance: karaf.
It means that we will have the following goals:
karaf:features
karaf:features-to-repo
karaf:run
karaf:dist
karaf:branding
WDYT ?
Thanks
Regards
JB
Re: Rename karaf features plugin with a more generic name
Posted by Andreas Pieber <an...@gmail.com>.
Both goals are currently available via
<groupId>org.apache.karaf.tooling</groupId>
<artifactId>features-maven-plugin</artifactId>
See [1] for an example of "karaf:"features-to-repo
This kopies the .jar files defined in the features.xml to a folder. features
creates a feature file from a pom.
kind regards,
andreas
[1] http://svn.apache.org/repos/asf/karaf/trunk/assembly/pom.xml
On Fri, Jan 14, 2011 at 08:25:34AM +0100, Charles Moulliard wrote:
> +1
>
> Question : What is supposed to do karaf:features and
> karaf:features-to-repo ? Generating the feature file from what the
> user defined under src/main/filtered-resources ?
>
>
> On Thu, Jan 13, 2011 at 5:05 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> > Hi again :)
> >
> > Sorry to disturb you again :).
> >
> > In Karaf tooling, we have the features maven plugin to generate the features
> > descriptor and copy the resources from the repo.
> >
> > We begin to see some requirement to new maven goals such as:
> > - karaf:run to run a Karaf instance from maven
> > - karaf:dist to create a Karaf distribution
> > - karaf:branding to create a Karaf branding bundle
> > - karaf:shell to connect to a Karaf instance remotely and bind the shell
> > - etc, etc
> >
> > As you can see, I voluntarily define several goals of the same maven plugin.
> >
> > I propose to refactore the existing features maven plugin by renaming it
> > with a more generic naming.
> > For instance: karaf.
> >
> > It means that we will have the following goals:
> > karaf:features
> > karaf:features-to-repo
> > karaf:run
> > karaf:dist
> > karaf:branding
> >
> > WDYT ?
> >
> > Thanks
> > Regards
> > JB
> >
Re: Rename karaf features plugin with a more generic name
Posted by Charles Moulliard <cm...@gmail.com>.
+1
Question : What is supposed to do karaf:features and
karaf:features-to-repo ? Generating the feature file from what the
user defined under src/main/filtered-resources ?
On Thu, Jan 13, 2011 at 5:05 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi again :)
>
> Sorry to disturb you again :).
>
> In Karaf tooling, we have the features maven plugin to generate the features
> descriptor and copy the resources from the repo.
>
> We begin to see some requirement to new maven goals such as:
> - karaf:run to run a Karaf instance from maven
> - karaf:dist to create a Karaf distribution
> - karaf:branding to create a Karaf branding bundle
> - karaf:shell to connect to a Karaf instance remotely and bind the shell
> - etc, etc
>
> As you can see, I voluntarily define several goals of the same maven plugin.
>
> I propose to refactore the existing features maven plugin by renaming it
> with a more generic naming.
> For instance: karaf.
>
> It means that we will have the following goals:
> karaf:features
> karaf:features-to-repo
> karaf:run
> karaf:dist
> karaf:branding
>
> WDYT ?
>
> Thanks
> Regards
> JB
>
Re: Rename karaf features plugin with a more generic name
Posted by Charles Moulliard <cm...@gmail.com>.
+1
Question : What are supposed to do the following goals ?
karaf:features
karaf:features-to-repo
On Thu, Jan 13, 2011 at 5:05 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi again :)
>
> Sorry to disturb you again :).
>
> In Karaf tooling, we have the features maven plugin to generate the features
> descriptor and copy the resources from the repo.
>
> We begin to see some requirement to new maven goals such as:
> - karaf:run to run a Karaf instance from maven
> - karaf:dist to create a Karaf distribution
> - karaf:branding to create a Karaf branding bundle
> - karaf:shell to connect to a Karaf instance remotely and bind the shell
> - etc, etc
>
> As you can see, I voluntarily define several goals of the same maven plugin.
>
> I propose to refactore the existing features maven plugin by renaming it
> with a more generic naming.
> For instance: karaf.
>
> It means that we will have the following goals:
> karaf:features
> karaf:features-to-repo
> karaf:run
> karaf:dist
> karaf:branding
>
> WDYT ?
>
> Thanks
> Regards
> JB
>
Re: Rename karaf features plugin with a more generic name
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Ok it's fine for me too ;)
Regards
JB
-----Original Message-----
From: Andreas Pieber <an...@gmail.com>
Date: Thu, 13 Jan 2011 18:12:20
To: <de...@karaf.apache.org>
Reply-To: dev@karaf.apache.org
Subject: Re: Rename karaf features plugin with a more generic name
According to the sonatype maven book (sry for being to lazy to search the
specific part) both are ok (that's why I actually mentioned both). But still,
I personally also prefer karaf-maven-plugin ;)
kind regards,
andreas
On Thu, Jan 13, 2011 at 08:59:58AM -0800, Guillaume Nodet wrote:
> The convention seems to be karaf-maven-plugin for plugins that do not come
> from maven I think.
> See http://www.mail-archive.com/users@maven.apache.org/msg23269.html
>
> On Thu, Jan 13, 2011 at 08:32, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> > I prefer maven-karaf-plugin to use the same nomenclature used in maven.
> >
> > Regards
> > JB
> >
> >
> > On 01/13/2011 05:32 PM, Andreas Pieber wrote:
> >
> >> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
> >>
> >> kind regards,
> >> andreas
> >>
> >> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
> >>
> >>> Hi again :)
> >>>
> >>> Sorry to disturb you again :).
> >>>
> >>> In Karaf tooling, we have the features maven plugin to generate the
> >>> features descriptor and copy the resources from the repo.
> >>>
> >>> We begin to see some requirement to new maven goals such as:
> >>> - karaf:run to run a Karaf instance from maven
> >>> - karaf:dist to create a Karaf distribution
> >>> - karaf:branding to create a Karaf branding bundle
> >>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
> >>> - etc, etc
> >>>
> >>> As you can see, I voluntarily define several goals of the same maven
> >>> plugin.
> >>>
> >>> I propose to refactore the existing features maven plugin by
> >>> renaming it with a more generic naming.
> >>> For instance: karaf.
> >>>
> >>> It means that we will have the following goals:
> >>> karaf:features
> >>> karaf:features-to-repo
> >>> karaf:run
> >>> karaf:dist
> >>> karaf:branding
> >>>
> >>> WDYT ?
> >>>
> >>> Thanks
> >>> Regards
> >>> JB
> >>>
> >>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: Rename karaf features plugin with a more generic name
Posted by Andreas Pieber <an...@gmail.com>.
According to the sonatype maven book (sry for being to lazy to search the
specific part) both are ok (that's why I actually mentioned both). But still,
I personally also prefer karaf-maven-plugin ;)
kind regards,
andreas
On Thu, Jan 13, 2011 at 08:59:58AM -0800, Guillaume Nodet wrote:
> The convention seems to be karaf-maven-plugin for plugins that do not come
> from maven I think.
> See http://www.mail-archive.com/users@maven.apache.org/msg23269.html
>
> On Thu, Jan 13, 2011 at 08:32, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> > I prefer maven-karaf-plugin to use the same nomenclature used in maven.
> >
> > Regards
> > JB
> >
> >
> > On 01/13/2011 05:32 PM, Andreas Pieber wrote:
> >
> >> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
> >>
> >> kind regards,
> >> andreas
> >>
> >> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
> >>
> >>> Hi again :)
> >>>
> >>> Sorry to disturb you again :).
> >>>
> >>> In Karaf tooling, we have the features maven plugin to generate the
> >>> features descriptor and copy the resources from the repo.
> >>>
> >>> We begin to see some requirement to new maven goals such as:
> >>> - karaf:run to run a Karaf instance from maven
> >>> - karaf:dist to create a Karaf distribution
> >>> - karaf:branding to create a Karaf branding bundle
> >>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
> >>> - etc, etc
> >>>
> >>> As you can see, I voluntarily define several goals of the same maven
> >>> plugin.
> >>>
> >>> I propose to refactore the existing features maven plugin by
> >>> renaming it with a more generic naming.
> >>> For instance: karaf.
> >>>
> >>> It means that we will have the following goals:
> >>> karaf:features
> >>> karaf:features-to-repo
> >>> karaf:run
> >>> karaf:dist
> >>> karaf:branding
> >>>
> >>> WDYT ?
> >>>
> >>> Thanks
> >>> Regards
> >>> JB
> >>>
> >>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: Rename karaf features plugin with a more generic name
Posted by Ioannis Canellos <io...@gmail.com>.
Indeed,
like camel-maven-plugin or jetty-maven-plugin.
On Thu, Jan 13, 2011 at 6:59 PM, Guillaume Nodet <gn...@gmail.com> wrote:
> The convention seems to be karaf-maven-plugin for plugins that do not come
> from maven I think.
> See http://www.mail-archive.com/users@maven.apache.org/msg23269.html
>
> On Thu, Jan 13, 2011 at 08:32, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> > I prefer maven-karaf-plugin to use the same nomenclature used in maven.
> >
> > Regards
> > JB
> >
> >
> > On 01/13/2011 05:32 PM, Andreas Pieber wrote:
> >
> >> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin
> :)
> >>
> >> kind regards,
> >> andreas
> >>
> >> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
> >>
> >>> Hi again :)
> >>>
> >>> Sorry to disturb you again :).
> >>>
> >>> In Karaf tooling, we have the features maven plugin to generate the
> >>> features descriptor and copy the resources from the repo.
> >>>
> >>> We begin to see some requirement to new maven goals such as:
> >>> - karaf:run to run a Karaf instance from maven
> >>> - karaf:dist to create a Karaf distribution
> >>> - karaf:branding to create a Karaf branding bundle
> >>> - karaf:shell to connect to a Karaf instance remotely and bind the
> shell
> >>> - etc, etc
> >>>
> >>> As you can see, I voluntarily define several goals of the same maven
> >>> plugin.
> >>>
> >>> I propose to refactore the existing features maven plugin by
> >>> renaming it with a more generic naming.
> >>> For instance: karaf.
> >>>
> >>> It means that we will have the following goals:
> >>> karaf:features
> >>> karaf:features-to-repo
> >>> karaf:run
> >>> karaf:dist
> >>> karaf:branding
> >>>
> >>> WDYT ?
> >>>
> >>> Thanks
> >>> Regards
> >>> JB
> >>>
> >>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
--
*Ioannis Canellos*
http://iocanel.blogspot.com
Integration Engineer @ Upstream S.A. <http://www.upstreamsystems.com>
Re: Rename karaf features plugin with a more generic name
Posted by Guillaume Nodet <gn...@gmail.com>.
The convention seems to be karaf-maven-plugin for plugins that do not come
from maven I think.
See http://www.mail-archive.com/users@maven.apache.org/msg23269.html
On Thu, Jan 13, 2011 at 08:32, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> I prefer maven-karaf-plugin to use the same nomenclature used in maven.
>
> Regards
> JB
>
>
> On 01/13/2011 05:32 PM, Andreas Pieber wrote:
>
>> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
>>
>> kind regards,
>> andreas
>>
>> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
>>
>>> Hi again :)
>>>
>>> Sorry to disturb you again :).
>>>
>>> In Karaf tooling, we have the features maven plugin to generate the
>>> features descriptor and copy the resources from the repo.
>>>
>>> We begin to see some requirement to new maven goals such as:
>>> - karaf:run to run a Karaf instance from maven
>>> - karaf:dist to create a Karaf distribution
>>> - karaf:branding to create a Karaf branding bundle
>>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
>>> - etc, etc
>>>
>>> As you can see, I voluntarily define several goals of the same maven
>>> plugin.
>>>
>>> I propose to refactore the existing features maven plugin by
>>> renaming it with a more generic naming.
>>> For instance: karaf.
>>>
>>> It means that we will have the following goals:
>>> karaf:features
>>> karaf:features-to-repo
>>> karaf:run
>>> karaf:dist
>>> karaf:branding
>>>
>>> WDYT ?
>>>
>>> Thanks
>>> Regards
>>> JB
>>>
>>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Rename karaf features plugin with a more generic name
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for the warning David.
Guillaume already mentioned that.
Regards
JB
On 01/13/2011 06:50 PM, David Jencks wrote:
> Please pay attention to the recommended plugin naming conventions. Only plugins maintained at apache in the maven project itself are supposed to be named maven-*-plugin. Since this is not one of them, it should be *-maven-plugin
>
> thanks
> david jencks
>
> On Jan 13, 2011, at 8:32 AM, Jean-Baptiste Onofré wrote:
>
>> I prefer maven-karaf-plugin to use the same nomenclature used in maven.
>>
>> Regards
>> JB
>>
>> On 01/13/2011 05:32 PM, Andreas Pieber wrote:
>>> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
>>>
>>> kind regards,
>>> andreas
>>>
>>> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
>>>> Hi again :)
>>>>
>>>> Sorry to disturb you again :).
>>>>
>>>> In Karaf tooling, we have the features maven plugin to generate the
>>>> features descriptor and copy the resources from the repo.
>>>>
>>>> We begin to see some requirement to new maven goals such as:
>>>> - karaf:run to run a Karaf instance from maven
>>>> - karaf:dist to create a Karaf distribution
>>>> - karaf:branding to create a Karaf branding bundle
>>>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
>>>> - etc, etc
>>>>
>>>> As you can see, I voluntarily define several goals of the same maven plugin.
>>>>
>>>> I propose to refactore the existing features maven plugin by
>>>> renaming it with a more generic naming.
>>>> For instance: karaf.
>>>>
>>>> It means that we will have the following goals:
>>>> karaf:features
>>>> karaf:features-to-repo
>>>> karaf:run
>>>> karaf:dist
>>>> karaf:branding
>>>>
>>>> WDYT ?
>>>>
>>>> Thanks
>>>> Regards
>>>> JB
>
--
Jean-Baptiste Onofré
---------------------------------
HomePage
http://www.nanthrax.net
---------------------------------
Contacts
jbonofre@apache.org
jb@nanthrax.net
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
Re: Rename karaf features plugin with a more generic name
Posted by David Jencks <da...@yahoo.com>.
Please pay attention to the recommended plugin naming conventions. Only plugins maintained at apache in the maven project itself are supposed to be named maven-*-plugin. Since this is not one of them, it should be *-maven-plugin
thanks
david jencks
On Jan 13, 2011, at 8:32 AM, Jean-Baptiste Onofré wrote:
> I prefer maven-karaf-plugin to use the same nomenclature used in maven.
>
> Regards
> JB
>
> On 01/13/2011 05:32 PM, Andreas Pieber wrote:
>> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
>>
>> kind regards,
>> andreas
>>
>> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
>>> Hi again :)
>>>
>>> Sorry to disturb you again :).
>>>
>>> In Karaf tooling, we have the features maven plugin to generate the
>>> features descriptor and copy the resources from the repo.
>>>
>>> We begin to see some requirement to new maven goals such as:
>>> - karaf:run to run a Karaf instance from maven
>>> - karaf:dist to create a Karaf distribution
>>> - karaf:branding to create a Karaf branding bundle
>>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
>>> - etc, etc
>>>
>>> As you can see, I voluntarily define several goals of the same maven plugin.
>>>
>>> I propose to refactore the existing features maven plugin by
>>> renaming it with a more generic naming.
>>> For instance: karaf.
>>>
>>> It means that we will have the following goals:
>>> karaf:features
>>> karaf:features-to-repo
>>> karaf:run
>>> karaf:dist
>>> karaf:branding
>>>
>>> WDYT ?
>>>
>>> Thanks
>>> Regards
>>> JB
Re: Rename karaf features plugin with a more generic name
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I prefer maven-karaf-plugin to use the same nomenclature used in maven.
Regards
JB
On 01/13/2011 05:32 PM, Andreas Pieber wrote:
> +1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
>
> kind regards,
> andreas
>
> On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
>> Hi again :)
>>
>> Sorry to disturb you again :).
>>
>> In Karaf tooling, we have the features maven plugin to generate the
>> features descriptor and copy the resources from the repo.
>>
>> We begin to see some requirement to new maven goals such as:
>> - karaf:run to run a Karaf instance from maven
>> - karaf:dist to create a Karaf distribution
>> - karaf:branding to create a Karaf branding bundle
>> - karaf:shell to connect to a Karaf instance remotely and bind the shell
>> - etc, etc
>>
>> As you can see, I voluntarily define several goals of the same maven plugin.
>>
>> I propose to refactore the existing features maven plugin by
>> renaming it with a more generic naming.
>> For instance: karaf.
>>
>> It means that we will have the following goals:
>> karaf:features
>> karaf:features-to-repo
>> karaf:run
>> karaf:dist
>> karaf:branding
>>
>> WDYT ?
>>
>> Thanks
>> Regards
>> JB
Re: Rename karaf features plugin with a more generic name
Posted by Andreas Pieber <an...@gmail.com>.
+1 to rename current plugin to maven-karaf-plugin or karaf-maven-plugin :)
kind regards,
andreas
On Thu, Jan 13, 2011 at 05:05:58PM +0100, Jean-Baptiste Onofré wrote:
> Hi again :)
>
> Sorry to disturb you again :).
>
> In Karaf tooling, we have the features maven plugin to generate the
> features descriptor and copy the resources from the repo.
>
> We begin to see some requirement to new maven goals such as:
> - karaf:run to run a Karaf instance from maven
> - karaf:dist to create a Karaf distribution
> - karaf:branding to create a Karaf branding bundle
> - karaf:shell to connect to a Karaf instance remotely and bind the shell
> - etc, etc
>
> As you can see, I voluntarily define several goals of the same maven plugin.
>
> I propose to refactore the existing features maven plugin by
> renaming it with a more generic naming.
> For instance: karaf.
>
> It means that we will have the following goals:
> karaf:features
> karaf:features-to-repo
> karaf:run
> karaf:dist
> karaf:branding
>
> WDYT ?
>
> Thanks
> Regards
> JB