You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2017/02/28 07:23:45 UTC

[jira] [Closed] (SLING-6556) slingstart-maven-plugin: Allow to reference the artifact which is being built by the same project as main artifact

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

Konrad Windszus closed SLING-6556.
----------------------------------

> slingstart-maven-plugin: Allow to reference the artifact which is being built by the same project as main artifact
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6556
>                 URL: https://issues.apache.org/jira/browse/SLING-6556
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Slingstart Maven Plugin 1.7.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Slingstart Maven Plugin 1.7.2
>
>
> Currently the slingstart-maven-plugin does not allow to reference the artifact within the model definition which is built by the current module. This restriction should be lifted to allow to consume those artifacts in case they have been built already (i.e. if goal `prepare-package` is bound to a phase after `package`). This is useful for having ITs in the same Maven module as the the actual bundle which should be tested.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)