Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.5
-
Fix Version/s: 1.8
-
Labels:None
-
Number of attachments :
Description
I've set up mavenHome in my POM to use Maven 2.2.1 but i have set a rule (invoker.maven.version = 2.2.0+, !3.0.0+) but the integration test is skipped anyway.
An assumtion of Rober Scholte was that invoker.maven.version works only for the executing Maven version which looks like. This results in two choices: either this is a bug or it should be clearly documented for the invoker.maven.version
Issue Links
- is related to
-
MINVOKER-106
invoker.java.version is always evaluated against current JVM instead of JVM running the builds
-
Activity
Robert Scholte
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is related to |
Robert Scholte
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Assignee | Robert Scholte [ rfscholte ] | |
| Fix Version/s | 1.8 [ 18730 ] | |
| Resolution | Fixed [ 1 ] |
Added the ability to get the version based on the MavenHome in r1402983.
I've seen it working on my Win7 machine with M2.2.1 and M3.0.1, so this looks promising.
Next step requires some refactoring of the original code, since it calculates this value for every buildjob, which is way too expensive in my opinion.