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é <[email protected]> > 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 > >
pgpTldwEYdmfp.pgp
Description: PGP signature
