[ https://issues.apache.org/jira/browse/MSHARED-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated MSHARED-1010: ------------------------------------- Description: 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 setter method. This is particularly crucial when multiple verifier instances are used in multiple threads, as each may leverage a different Maven home directory. was: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 setter method. > Allow to customize Maven home > ----------------------------- > > Key: MSHARED-1010 > URL: https://issues.apache.org/jira/browse/MSHARED-1010 > Project: Maven Shared Components > Issue Type: Bug > Reporter: Konrad Windszus > Priority: Major > > 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 setter method. > This is particularly crucial when multiple verifier instances are used in > multiple threads, as each may leverage a different Maven home directory. -- This message was sent by Atlassian Jira (v8.20.1#820001)