Maybe I found an explanation for the location.
Current 'global' isn't really global. It's bound to the Maven
installation. So for instance: whenever you upgrade your Maven, you
shouldn't forget to copy the settings.xml.
By putting it under the user.home, you'll never have to change it.
So it works, but IMHO for the wrong reason.
Makes we wonder if we need to think of a real global location as well...
Robert
Op Sun, 19 Oct 2014 18:18:34 +0200 schreef Robert Scholte
<[email protected]>:
Hi,
since we're slowly upgrading the minimum JDK to run Maven it becomes
more and more important to let our users know how they can compile with
an ancient/older version of the JDK. I think we all agree that
toolchains is the way to go.
I proposed to add the toolchains to the Maven distribution and already
got a couple of +1's for that idea.
However, it seems like the toolchain.xml is a user specific file and not
a global file. [1]
Putting this file under /conf of the distribution (next to the global
settings.xml) would probably confuse a lot of people it that file is not
picked up from that location.
Actually, I would say that tools are system specific and not just user
specific.
Is there any historic reason to configure it per user?
Should we support global toolchains as well?
thanks,
Robert
[1] http://maven.apache.org/guides/mini/guide-using-toolchains.html (
The toolchains.xml file (see below) is the configuration file where you
set the installation paths of your toolchains. This file should be put
in your $user.home/.m2 directory. )
---------------------------------------------------------------------
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]
