[ 
https://issues.apache.org/activemq/browse/SMX4KNL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50195#action_50195
 ] 

Charles Moulliard commented on SMX4KNL-217:
-------------------------------------------

Most of the time, when you work on a OSGI project, you will create in eclipse 
several eclipse projects, one by bundle. So, it makes sense to create a parent 
pom pointing to the different modules / bundles and to have one global features 
file.

Here is an example of what I do manually to deploy all my bundles :

<features>
<feature name="reportincident" version="1.0">
        <feature>camel-core</feature>
        <feature>camel-spring</feature>
        <feature>camel-osgi</feature>
        <feature>camel-bindy</feature>
        <feature>server</feature>
        
<bundle>mvn:org.apache.camel.example/reportincident.domain/1.0-SNAPSHOT</bundle>
        
<bundle>mvn:org.apache.camel.example/reportincident.service/1.0-SNAPSHOT</bundle>
        
<bundle>mvn:org.apache.camel.example/reportincident.interfaces/1.0-SNAPSHOT</bundle>
            
</feature>

reportincident.domain = maven project = bundle = eclipse project



> Enhance features maven plugin to support deployment / undeployment of 
> features, html generation and create a few archetypes
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SMX4KNL-217
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-217
>             Project: ServiceMix Kernel
>          Issue Type: New Feature
>            Reporter: Charles Moulliard
>            Assignee: Edell Nolan
>
> Enhance the features maven plugin 
> (http://svn.apache.org/repos/asf/servicemix/maven-plugins/features-maven-plugin)
>  to support :
> 1) Deployment / undeployment of features,
> 2) Generate html page about features  : see 
> http://fusesource.com/forums/message.jspa?messageID=2005#2005 for the 
> suggestion
> 3) Creation a few archetypes:
>   - one for creating a custom smx kernel distribution + a set of
> features (like what we do for our distributions). 
>   - one for creating a feature descriptor automatically generated
> using the maven plugin we already have + upload in the maven repo. Ideally, 
> the descriptor should be created from the user pom.xml profile file or 
> (pom.xml files if the user has created a parent pom.xml with modules)
>   - one for creating a manually written feature descriptor + upload in
> the maven repo
> The two last archetypes should reference our maven plugin so that they
> could be easily installed / uninstalled to a running (or not) smx4
> kernel instance using maven.
> Remark : this ticket has been created following discussions exchanged in the 
> forum of SMX : http://www.nabble.com/forum/ViewPost.jtp?post=22285345&framed=y

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to