[
https://issues.apache.org/jira/browse/KARAF-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Roedl updated KARAF-1223:
-------------------------------
Attachment: CreateKarMojo.java.patch
I also find the use case to create kar over existing features (present on a
repo) interesting.
And furthermore it would solve my problem ;-)
I've updated the patch: The plugin now tries to resolve artifacts that don't
exist in the local repo.
> 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
> Assignee: Jean-Baptiste Onofré
> 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
