maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Raumberger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6117) ${session.parallel} not correctly set
Date Sun, 13 Nov 2016 20:11:58 GMT

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

Richard Raumberger commented on MNG-6117:
-----------------------------------------

I'm sorry for the misunderstanding. I wasn't aware of the fact, that this special behaviour
exists for the {{MultiThreadedBuilder}}. The behaviour does make sense, though.

A valid example using the correct amount of threads, which avoids the mentioned special behaviour
can be found [here|https://cloud.almost-a-blog.net/s/dUmO2mZha5hzqB3/download]. Which results
in {{session.parallel}} to be {{false}} for all threads, when run with {{mvn clean test -T
3 | grep isParallel}}.
If the same command is executed with Maven 3.0.5 the property is correctly set.

Your fix sounds ok for me.

> ${session.parallel} not correctly set
> -------------------------------------
>
>                 Key: MNG-6117
>                 URL: https://issues.apache.org/jira/browse/MNG-6117
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.3.9
>            Reporter: Richard Raumberger
>
> Running {{mvn help:evaluate -T 3}} and resolving the property  {{session.parallel}} returns
{{true}} when run with Maven 3.0.5.
> When running it with 3.3.9, this property resolves to {{false}}.
> {code}
> mvn help:evaluate -T 3
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of 3
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-help-plugin:2.2:evaluate (default-cli) @ standalone-pom ---
> [INFO] No artifact parameter specified, using 'org.apache.maven:standalone-pom:pom:1'
as project.
> [INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
> ${session.parallel}
> [INFO]
> false
> {code}
> E.g. Surefire [relies|https://github.com/apache/maven-surefire/blob/fb9b699e27dae905393a5bc4d5c6ae39606c3172/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L658]
on this property, to check whether Maven is running in parallel mode, as mentioned in the
comments of [SUREFIRE-1301|https://issues.apache.org/jira/browse/SUREFIRE-1301].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message