[
https://issues.apache.org/jira/browse/MINVOKER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958339#comment-17958339
]
Olivier Lamy commented on MINVOKER-106:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#378|https://github.com/apache/maven-invoker-plugin/issues/378].
> invoker.java.version is always evaluated against current JVM instead of JVM
> running the builds
> ----------------------------------------------------------------------------------------------
>
> Key: MINVOKER-106
> URL: https://issues.apache.org/jira/browse/MINVOKER-106
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: Benjamin Bentmann
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 1.8
>
>
> The selector condition for the JVM version always looks at the current JVM,
> not the JVM that will be used to run the forked builds. This gets only
> obvious when using invoker.javaHome to point at a different JVM than the one
> running the Invoker Plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
