[
https://issues.apache.org/jira/browse/KARAF-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215197#comment-13215197
]
David Jencks commented on KARAF-1223:
-------------------------------------
Can you explain what you are trying to do? It seems to me that you are trying
to break a lot of basic important maven conventions for unexplained reasons.
- one project creates one artifact. So if you want more than one kar file,
have more than one project.
- the primary goal of the feature packaging and kar packaging is to produce a
single feature.xml from maven dependencies (feature packaging) or use this
generated feature.xml to also construct a kar. You can aggregate other feature
repos by listing them as maven dependencies and using the aggregate flag or
include them as dependencies of the generated feature in the feature.xml by not
using the aggregate flag.
Neither the feature mojo or kar mojo are intended to be used outside the
feature or kar packaging.
If you are trying to get the mojos to support another use case, can you explain
it fully?
> Support mvn:* urls in karaf-maven-plugin:features-create-kar
> ------------------------------------------------------------
>
> Key: KARAF-1223
> URL: https://issues.apache.org/jira/browse/KARAF-1223
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Reporter: Lukas Roedl
> Fix For: 3.0.0
>
> Attachments: CreateKarMojo.java.patch
>
>
> The features-create-kar goal of the karaf-maven-plugin plugin currently only
> supports references to local feature files. The featuresFile tag should also
> support mvn:* urls.
> This may also avoid the following problem if the features file is added with
> the correct groupId/artifactId.
> In a single pom the karaf-maven-plugin with goal features-create-kar is
> executed twice to generate two separate kar files from two independent
> features.xml files.
> The resulting kar files are deployed to the "deploy" folder and at Karaf's
> startup it seems that only one of them is loaded.
> The plugin adds the feature files with the same groupId/artifactId to the kar
> files and while deploying they overwrite each other.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
