[
https://issues.apache.org/jira/browse/MSHARED-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503139#comment-17503139
]
Hudson commented on MSHARED-1010:
---------------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven-verifier » master #6
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-verifier/job/master/6/
> Allow to customize Maven home
> -----------------------------
>
> Key: MSHARED-1010
> URL: https://issues.apache.org/jira/browse/MSHARED-1010
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-verifier
> Reporter: Konrad Windszus
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: maven-verifier-2.0.0
>
>
> In order to run ITs against multiple versions of Maven, it would be
> beneficial, if the Maven version cannot only be customised implicitly via
> System properties
> (https://github.com/apache/maven-verifier/blob/246edfd46a2953f18099864cffb61257c0f2d698/src/main/java/org/apache/maven/it/Verifier.java#L200-L215),
> but also more explicitly via a constructor argument.
> This is particularly crucial when multiple verifier instances are used in
> multiple threads, as each may leverage a different Maven home directory.
> In case a Maven home directory is explicitly set it should take precedence
> over mvnw.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
