Op Sat, 01 Nov 2014 14:56:56 +0100 schreef Hervé BOUTEMY <[email protected]>:

Le samedi 1 novembre 2014 23:45:32 Mark Derricutt a écrit :
On 1 Nov 2014, at 22:41, Dennis Lundberg wrote:
> so that we can update it quickly when new plugins support it. The others
> should just link to that page. The current info on supporting
+1
this could be the mini guide, transforming "Below are some plugins which are JDK-toolchain-aware" to a proper section intended to list which plugins are
known to be JDK-toolchain-aware


For reference - my clojure-maven-plugin has supported it for ages now, and I
think I rolled that over onto my frege-maven-plugin as well ( can't
remember if I did or not now ).

I think it'd be good if maven shipped with a system/distro toolchains.xml
that at least say, declared a "system" JDK chain pointing at say
$JAVA_HOME.
great idea!
will require MNG-3891, to have effective toolchains.xml after merging distro conf with user conf, like done with settings: should not be hard to do, just
follow settings example
and it will probably be useful to have a toolchains:effective-toolchains mojo
to display the effective toolchains

any volunteer?

I'll pick up the merger. Should also help me to understand how to generate this with modello in the end.



And possibly included a default configuration in the super-pom for the said
system JDK.
then toolchains would be used by default: do you see a way to disable it, in
case of unexpected problem?
this idea is interesting, but I fear it will cause unexpected edge cases...


This gives us 2 points of instant reference:

1) How to configure a toolchain, cp the system toolchains.xml to your .m2
and modify
+1, like settings.xml
2) How to configure the maven-toolchain-plugin to
request/override toolchains.
we'll probably need combine.self="override": will need explanation for normal
end-user...

Regards,

Hervé


Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to