You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Grzegorz Grzybek (JIRA)" <ji...@apache.org> on 2017/07/12 11:06:00 UTC

[jira] [Assigned] (KARAF-5164) karaf-maven-plugin fails to verify artifacts if only available within local reactor

     [ https://issues.apache.org/jira/browse/KARAF-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Grzybek reassigned KARAF-5164:
---------------------------------------

    Assignee: Grzegorz Grzybek

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