[
https://issues.apache.org/activemq/browse/SMX4KNL-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50270#action_50270
]
Charles Moulliard commented on SMX4KNL-217:
-------------------------------------------
Edell,
It should be interesting that the plugin works also with pom where <module> are
defined.
This could be very helpful because the feature file generated could be the sum
of the features file created for each pom sub-project. Therefore, we have only
one file to use to deploy our application containing different bundles (dao,
domain, services, web, ...
Name of the project : ReportIncident (= parent pom)
module : dao
module : domain
module : service
For each module, we have a feature file.
When we launch mvn install (parent pom), the report incident feature file is
generated and contains :
<features
<feature name='dao'/>
<feature name='domain'/>
<feature name='service'/>
<feature name='dao version='A.0-SNAPSHOT'>
<bundle>mvn:org.apache.camel.example/reportincident.dao/1.0-SNAPSHOT</bundle>
<bundle>mvn:org.apache.camel/camel-core/1.6.0</bundle>
<mvn: .....>
</feature>
...
</features>
> 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
> Attachments: SMXKNL-217-feature.patch
>
>
> 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.