[
https://issues.apache.org/jira/browse/KARAF-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated KARAF-497:
----------------------------------
Attachment: KARAF-497.diff
Perhaps there's a better way to handle this in Karaf 3.x with karaf-assembly
packaging, but for Karaf 2.x we can get this working with the simple patch I'm
attaching to this issue.
This little patch would resolve a descriptor before trying to read it, ensuring
that it is available in the local repository before reading it. The same thing
already happens for bundles specified in the features files being handled, so
I'm not sure why this little addition would be such a big problem.
> Resolve mvn: urls in <features/> element for
> features-maven-plugin:add-features-to-repo
> ---------------------------------------------------------------------------------------
>
> Key: KARAF-497
> URL: https://issues.apache.org/jira/browse/KARAF-497
> Project: Karaf
> Issue Type: Improvement
> Components: tooling
> Affects Versions: 2.2.0
> Reporter: Gert Vanthienen
> Fix For: 2.2.1, 3.0.0
>
> Attachments: KARAF-497.diff
>
>
> When setting up features-maven-plugin:add-features-to-repo with a mvn: url in
> the <features/> element, it would be nice if the plugin could resolve the
> artifact before trying to load the file to avoid having to specify an
> explicit dependency to fetch the file first.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
