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
[email protected]
[email protected]
---------------------------------
OpenSource
BuildProcess/AutoDeploy
http://buildprocess.sourceforge.net
Apache ServiceMix
http://servicemix.apache.org
-----------------------------------
PGP : 17D4F086
