Maven Invoker Plugin
  1. Maven Invoker Plugin
  2. MINVOKER-106

invoker.java.version is always evaluated against current JVM instead of JVM running the builds

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.8
    • Labels:
      None
    • Number of attachments :
      0

      Description

      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.

        Issue Links

          Activity

          Hide
          Robert Scholte added a comment -

          One way to figure it out is by calling

          {java.home}

          /bin/java -version and parse the output, but I'm not sure if this is vendor specific.

          Show
          Robert Scholte added a comment - One way to figure it out is by calling {java.home} /bin/java -version and parse the output, but I'm not sure if this is vendor specific.
          Hide
          Robert Scholte added a comment -

          We need to access the PluginDescriptor.getPluginArtifact(), M2.2.1 is the first stable Maven version which supports this.

          Show
          Robert Scholte added a comment - We need to access the PluginDescriptor.getPluginArtifact() , M2.2.1 is the first stable Maven version which supports this.
          Hide
          Robert Scholte added a comment -

          Fixed in r1408460

          Show
          Robert Scholte added a comment - Fixed in r1408460

            People

            • Assignee:
              Robert Scholte
              Reporter:
              Benjamin Bentmann
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: