maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5755) Access toolchains without maven-toolchain-plugin
Date Sun, 18 Jan 2015 15:56:19 GMT

     [ https://jira.codehaus.org/browse/MNG-5755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MNG-5755.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.6

Fixed in [4b263106db043f5c1d7c314237ab2bc8708c0538|http://git-wip-us.apache.org/repos/asf/maven/commit/4b263106]

> Access toolchains without maven-toolchain-plugin
> ------------------------------------------------
>
>                 Key: MNG-5755
>                 URL: https://jira.codehaus.org/browse/MNG-5755
>             Project: Maven
>          Issue Type: New Feature
>          Components: Toolchains
>    Affects Versions: 3.2.5
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>             Fix For: 3.2.6
>
>
> 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
(v6.1.6#6162)

Mime
View raw message