[
https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085590#comment-16085590
]
ASF subversion and git services commented on KARAF-5164:
--------------------------------------------------------
Commit 0de824307a6af15e49c80c7bfbdeff116d3e75ca in karaf's branch
refs/heads/master from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0de8243 ]
Merge branch 'grgrzybek-KARAF-5164-master'
> karaf-maven-plugin fails to verify artifacts if only available within local
> reactor
> -----------------------------------------------------------------------------------
>
> Key: KARAF-5164
> URL: https://issues.apache.org/jira/browse/KARAF-5164
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 4.2.0
> Reporter: Patrick Fink
> Assignee: Grzegorz Grzybek
> Priority: Minor
> Labels: maven
>
> When the karaf-maven-plugin is used as part of the build process (e.g. to
> verify features), it currently requires that the verified artifacts are
> available in the local repository while it's not sufficient that they're
> avaible within the local reactor.
> This means, build processes which contain the karaf-maven-plugin to verify
> features, fail when the user don't wants to install artifacts in their local
> repository. So,e.g.
> `mvn clean install` works fine and like expected while commands like
> `mvn clean package` or `mvn clean verify` will fail with resolution errors
> (if the artifacts just built are not already available within the local repo).
> The karaf-maven-plugin should support artifacts which are not available in
> the local repository, but in the local reactor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
