The convention seems to be karaf-maven-plugin for plugins that do not come from maven I think. See http://www.mail-archive.com/[email protected]/msg23269.html
On Thu, Jan 13, 2011 at 08:32, Jean-Baptiste Onofré <[email protected]> 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
