[
https://issues.apache.org/jira/browse/MINVOKER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958288#comment-17958288
]
Olivier Lamy commented on MINVOKER-58:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#307|https://github.com/apache/maven-invoker-plugin/issues/307].
> Allow to declare setup projects which must be run before all the rest
> ---------------------------------------------------------------------
>
> Key: MINVOKER-58
> URL: https://issues.apache.org/jira/browse/MINVOKER-58
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 1.2.1
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 1.3
>
>
> For the ITs of the maven-release-plugin I needed a stub SCM provider. To make
> sure its artifact is available for all the IT projects, it needs to be
> installed into the local repo first. Since the build order of the selected
> projects is in general undefined, this requires to configure two plugin
> executions with appropriate includes/excludes. To avoid this hassle, their
> should be an easy way to have some projects be guaranteed to be run ahead of
> the other builds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
