[jira] [Comment Edited] (SLING-10984) Starter IT: docker-maven-plugin:stop executed prior to feature-launcher-maven-plugin:stop

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus edited comment on SLING-10984 at 12/8/21, 3:01 PM:
-------------------------------------------------------------------

The reason is that 1.&2 and 3.&4. are bound to the same phases, so the order is determined by the order of plugins. A similar issue is described at https://stackoverflow.com/questions/55855968/maven-plugin-crossed-execution-order


was (Author: kwin):
The reason is that 1.&2 and 3.&4. are bound to the same phases, so the order is determined by the order of plugins. 

> Starter IT: docker-maven-plugin:stop executed prior to feature-launcher-maven-plugin:stop
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-10984
>                 URL: https://issues.apache.org/jira/browse/SLING-10984
>             Project: Sling
>          Issue Type: Bug
>          Components: Starter
>    Affects Versions: Starter 12
>            Reporter: Konrad Windszus
>            Priority: Major
>
> The order of the goals of {{docker-maven-plugin}} and {{feature-launcher-maven-plugin}} need to be executed in this order for the integration test
> # docker-maven-plugin:start
> # feature-launcher-maven-plugin:start
> # feature-launcher-maven-plugin:stop
> # docker-maven-plugin:stop
> But currently the docker container is stopped before the Sling feature is stopped.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)