[
https://issues.apache.org/jira/browse/KARAF-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015475#comment-13015475
]
Andreas Pieber commented on KARAF-497:
--------------------------------------
TBH I was never confronted by this problem and I'm with with David that it may
not be "best-practice" to do it that way and that all references should be
named in the pom... Though, I think it won't hurt to also support deps only
named in the features.xml. At least for 2.2 where the is not really another
("good") way to configure them. @David: is this ok with you?
> 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
