You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (Jira)" <ji...@apache.org> on 2020/04/17 16:51:00 UTC
[jira] [Resolved] (SUREFIRE-1692) surefire use jdkToolchain as per
compiler plugin
[ https://issues.apache.org/jira/browse/SUREFIRE-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tibor Digana resolved SUREFIRE-1692.
------------------------------------
Resolution: Duplicate
> surefire use jdkToolchain as per compiler plugin
> ------------------------------------------------
>
> Key: SUREFIRE-1692
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1692
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
> Affects Versions: 2.22.2, 3.0.0-M3
> Reporter: John Patrick
> Assignee: Tibor Digana
> Priority: Major
>
> I'm trying to create a multi-release project, supporting java 1.8 and java 11.
> My issue is I'm having a nightmare executing tests against both 1.8 and 11.
> Could surefire have an option like compile to configure the jdkToolchain.
> I understand that jvm is another config option, but that from what i'm reading requires the path to the java executable which isn't as helpful.
> I would like to add something like this;
> <configuration>
> <jdkToolchain>
> <version>11</version>
> </jdkToolchain>
> </configuration>
> or this;
> <executions>
> <execution>
> <id>java11</id>
> <phase>test</phase>
> <goals>
> <goal>test</goal>
> </goals>
> <configuration>
> <jdkToolchain>
> <version>11</version>
> </jdkToolchain>
> </configuration>
> </execution>
> </executions>
>
>
> Thinks might be planned, but at the moment I'm having a nightmare using toolchain executions but if i get surefire running with java 11 then following phases also use java 11 which means jar and javadoc fail in my current setup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)