You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2011/03/13 18:54:59 UTC

[jira] Commented: (KARAF-497) Resolve mvn: urls in element for features-maven-plugin:add-features-to-repo

    [ https://issues.apache.org/jira/browse/KARAF-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006231#comment-13006231 ] 

David Jencks commented on KARAF-497:
------------------------------------

IMO this is a terrible idea.  Maven projects should express their structure in the maven pom.  The only way this is plausible would be to construct a new kind of pom using polyglot maven.

The karaf-assembly packaging takes the alternate viewpoint that you only specify stuff as dependencies and all the dependencies are put into the assembled server.

Please justify or close this.

> 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
>
>
> 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