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
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
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
/Anders
On Wed, Feb 19, 2014 at 7:12 PM, Karl Heinz Marbaise khmarba...@gmx.dewrote:
Hi,
maybe
Hello Karl-Heinz,
you may take a look at
https://github.com/mfriedenhagen/org.jacoco.filteringsamples. These
are some code samples for JDK5, 6, 7 and 8, which will be asmified
(decompiled) to see differences in byte code produced by different
JDKs.
This is how the maven-compiler-plugin uses the
Hello Mirko,
Hello Anders,
this have been the information what i have missed...
Thanks for your help.
Kind regards.
Karl-Heinz
you may take a look at
https://github.com/mfriedenhagen/org.jacoco.filteringsamples. These
are some code samples for JDK5, 6, 7 and 8, which will be asmified
