You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/23 11:30:00 UTC

[jira] [Resolved] (MINVOKER-100) MavenVersion + ToolChain instead of mavenHome

     [ https://issues.apache.org/jira/browse/MINVOKER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold resolved MINVOKER-100.
--------------------------------------------
    Resolution: Abandoned

> MavenVersion + ToolChain instead of mavenHome
> ---------------------------------------------
>
>                 Key: MINVOKER-100
>                 URL: https://issues.apache.org/jira/browse/MINVOKER-100
>             Project: Maven Invoker Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.5
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Major
>         Attachments: MINVOKER-100.patch
>
>
> Jdk-paths are just as personal as maven-paths. It's already great to have the opportunity to change the mavenHome, but combining it with toolchain would provide an even more elegant way of defining the Maven installation to use. Just set the mavenVersion property of this plugin and let toolchain provide you the right mavenHome.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)