[
http://jira.codehaus.org/browse/MINVOKER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MINVOKER-100:
------------------------------------
Attachment: MINVOKER-100.patch
Let me give some background info.
Normally the toolchain plugin can be used so all plugins use the same version
of a specific tool.
With invoker it's a bit different. Here you explicitly try to use another
version of a tool, but the mechanism is the same.
I've added a custom (restricted) toolchains for invoker, since only java and
maven are tools which can be set by the invoker. For Maven were no factories or
toolchails available, so I've added them as well.
I've written some sort of IT as well, just to see if it would work on my
system. There's no way to change the path to the toolchains.xml, so it's not
possible to write a proper test.
Configuring the invoker with toolchains would look like this:
{code:xml}
<configuration>
<toolchains>
<jdk>
<version>[1.5.0_15]</version>
</jdk>
<maven>
<version>[2.0,)</version>
</maven>
</toolchains>
</configuration>
{code}
> MavenVersion + ToolChain instead of mavenHome
> ---------------------------------------------
>
> Key: MINVOKER-100
> URL: http://jira.codehaus.org/browse/MINVOKER-100
> Project: Maven 2.x Invoker Plugin
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Robert Scholte
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
