[Commented] (SUREFIRE-720) Toolchain is ignored

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[Commented] (SUREFIRE-720) Toolchain is ignored

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395576#comment-16395576 ]

Tibor Digana commented on SUREFIRE-720:

If you use {{forkCount}} this will happen. It's actually designed so because we are selecting what classes are supposed to be a valid test and these are spread out over the runtime JVMs. Therefore discovery of the classes is done within plugin's JVM however the execution is done in JDK9.
Try similar case with JDK 7 and JDK8 with older versions of the plugin and I guess you will end up with same problem because it was always designed like this.
I remember this issue in past but it is not possible to fix it now. We have to make certain redesign inside and this must be done in several versions like 3.0.0-M1 - 3.0.0-M2. After these redesign steps we would be capable to fix this as well.

> Toolchain is ignored
> --------------------
>                 Key: SUREFIRE-720
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-720
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8
>         Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\..
> Java version: 1.6.0_19, vendor: Sun Microsystems Inc.
> Java home: C:\Users\alex\Software\jdk1.6.0_19\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
>            Reporter: Jun
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 2.9
>         Attachments: SurefireToolchains.zip
> The following debug output demonstrates the problem:
> ...
> [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22]
> ...
> [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22]
> [WARNING] Toolchains are ignored, 'executable' parameter is set to C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java
> Forking command line: cmd.exe /X /C "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar
> ...
> Compiler plugin uses proper JDK, while Surefire falls back to default. The problem is not reproducible with Surefire 2.6 and 2.5.

This message was sent by Atlassian JIRA