You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Olivier Lamy (*$^¨%`£ Jira)" <ji...@apache.org> on 2019/09/05 00:53:00 UTC

[jira] [Assigned] (MINVOKER-174) The execution order of setupIncludes can't be predicted

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

Olivier Lamy (*$^¨%`£) reassigned MINVOKER-174:
-----------------------------------------------

    Assignee: Olivier Lamy (*$^¨%`£)

> The execution order of setupIncludes can't be predicted
> -------------------------------------------------------
>
>                 Key: MINVOKER-174
>                 URL: https://issues.apache.org/jira/browse/MINVOKER-174
>             Project: Maven Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.9
>            Reporter: Karl Heinz Marbaise
>            Assignee: Olivier Lamy (*$^¨%`£)
>            Priority: Critical
>
> It is really necessary to have at least one criteria which gives the possibility to define the order of executions of the setup projects which can be given by setupIncludes.
> Currently there is no such possibility. It should be at least possible to define the order by sorting in some way.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)