maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Volkert de Buisonjé (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (SUREFIRE-720) Toolchain is ignored
Date Tue, 13 Mar 2018 09:51:00 GMT

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

Volkert de Buisonjé edited comment on SUREFIRE-720 at 3/13/18 9:50 AM:
-----------------------------------------------------------------------

[~tibor17]
Thanks for clarifying this. So if this issue is limited to the test class discovery/distribution
step and the actual tests are still run using the configured JDK toolchain, am I right to
conclude that making sure that Maven itself always runs on the latest available JDK (or at
least on the most recent JDK version that you have configured in your toolchains.xml) would
be a full-proof workaround for this limitation?

Anyway, it might be a good idea to emphasize this current limitation in the documentation,
since I couldn't find any info about this on-line when I ran into it. 

Also, is there already an improvement issue or feature request in JIRA to fix this specific
limitation as part of such a future redesign effort of Maven?

Thanks. :)


was (Author: volkert):
[~tibor17]
Thanks for clarifying this. So if this issue is limited to the test class discovery step and
the actual tests are still run using the configured JDK toolchain, am I right to conclude
that making sure that Maven itself always runs on the latest available JDK (or at least on
the most recent JDK version that you have configured in your toolchains.xml) would be a full-proof
workaround for this limitation?

Anyway, it might be a good idea to emphasize this current limitation in the documentation,
since I couldn't find any info about this on-line when I ran into it. 

Also, is there already an improvement issue or feature request in JIRA to fix this specific
limitation as part of such a future redesign effort of Maven?

Thanks. :)

> 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
(v7.6.3#76005)

Mime
View raw message