Am Wed, 19 Feb 2014 19:17:03 +0100 schrieb Anders Hammar <and...@hammar.net>:
> One thing it can be used for is to define a different JDK to be used > (than the one used for executing Maven itself). More info here: > http://maven.apache.org/guides/mini/guide-using-toolchains.html What is quite interesting on this page, it talks about exec-maven-plugin, but not the maven-invoker-plugin. The later does require JDK homes and Maven Homes, both could be toolchained. In fact there is already a bug about it: https://jira.codehaus.org/browse/MINVOKER-100 We could think about providing the toolchain entries as special properties, then one could use: <mavenHome>${toolchain.mavenhome.3.0.x}</mavenHome> <javaHome>${toolchain.jdkhome.1.7.0.51}</javaHome> Or similiar? Gruss Bernd maven-invoker-plugin > > /Anders > > > On Wed, Feb 19, 2014 at 7:12 PM, Karl Heinz Marbaise > <khmarba...@gmx.de>wrote: > > > Hi, > > > > maybe i didn't see a thing, but can someone explain me the > > intention of the maven toolchain in relationship with a plugin ... > > > > Currently i only see that it can find some kind of executable which > > is configured in somekind of buildcontext...which i currently don't > > understand how to configure (I've taken a look into the > > maven-toolchains-plugin which didn't enlighten me)... > > > > But what are the advantages / disadvantages of that ? > > > > May be i just be blockhead ...;-( > > > > > > Kind regards > > Karl Heinz Marbaise > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
