[
https://issues.apache.org/jira/browse/MNG-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069574#comment-17069574
]
Hudson commented on MNG-5755:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> Access toolchains without maven-toolchain-plugin
> ------------------------------------------------
>
> Key: MNG-5755
> URL: https://issues.apache.org/jira/browse/MNG-5755
> Project: Maven
> Issue Type: New Feature
> Components: Toolchains
> Affects Versions: 3.2.5
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.3.1
>
>
> The original idea of toolchains was to have the same tool being used by
> different plugins within the same project.
> This seems like a good approach, but there are several cases where you want
> more control over the tool to choose, for instance:
> * the maven-compiler-plugin should use the lowest (preferably matching) jdk
> version to ensure proper bytecode for the classes
> * the maven-surefire-plugin might need a higher version due to requirements
> of the testing frameworks
> * some code-generators require a more recent JDK compared to the code they're
> actually producing.
> * the look-and-feel of javadoc has changed per JDK. If you like the latest,
> you should be able to use it.
> * In case of the maven-invoker-plugin you should be able to test all
> combinations of JDK and Maven as runtime environment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
