[
https://issues.apache.org/jira/browse/KARAF-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015487#comment-13015487
]
David Jencks commented on KARAF-497:
------------------------------------
I don't believe the add-features-to-repo mojo necessarily has a future in the
karaf-maven-plugin, but the code in 3.0.0 that does this stuff while assembling
a server from kars already fetches all the dependencies using aether resolution
directly so the dependencies don't need to be mentioned in the poms. I'm
hoping that everyone will assemble their features.xml files using the features
packaging so the dependencies will be coming from poms anyway. I didn't see a
reasonable way to code the server assembly without using aether directly.
> Resolve mvn: urls in <descriptor/> 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
