[
https://issues.apache.org/jira/browse/MNG-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106437#comment-16106437
]
Robert Scholte commented on MNG-6265:
-------------------------------------
I was looking for options which would help to get the same reliability with the
options that are already there. And I would prefer automatic solution when
possible. And I am quite critical with every new option added: is it really
required? And the number of lines changed/added is no criteria.
IMHO I don't think that order is really the key issue here. If C breaks the
build and you only change C, then there's no need to build A and B again,
unless you made changes there as well. So to me trying to run C, A, B is a sign
there's something else wrong.
There is already one argument which can contain multiple projects: {{-pl /
--project-list}}. Right now AFAIK its order has no effect, but I can imagine we
could make Maven respect that order, as long as the graph-order is respected!
In other words: if A, B and C have no relations, there order can be changed. If
C depends on A and B, it'll still be ABC.
> Controlling reactor order of modules
> ------------------------------------
>
> Key: MNG-6265
> URL: https://issues.apache.org/jira/browse/MNG-6265
> Project: Maven
> Issue Type: New Feature
> Components: core
> Affects Versions: 3.5.0
> Reporter: August Shi
> Attachments: p.patch
>
>
> We have a use case for controlling the reactor order in Maven, specifically
> for running tests on Travis. The common pattern is to run "mvn install
> -DskipTests; mvn test". After modules are installed (in the default order),
> the modules can be run in any order during testing, e.g., running the failed
> modules first, as in -Dsurefire.runOrder=failedfirst for Surefire.
> Would this feature be useful for others? I am attaching a *draft* patch that
> implements this feature by modifying DefaultMaven.java. I see no clean way of
> implementing this feature through an extension, unless some new callback,
> e.g., afterProjectsOrdered, is implemented first. Would it be worthwhile to
> improve this draft?
> One can test the feature by applying the patch, building Maven, and running
> tests with the modules in a random order like this:
> $ mvn -DdistributionTargetDir=$(pwd)/apache-maven-3.5.x-SNAPSHOT clean
> install -DskipTests
> $ apache-maven-3.5.x-SNAPSHOT/bin/mvn test -Dmaven.project.order.file=<(ls -d
> maven* | shuf)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
