maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Eckenfels <>
Subject Re: Toolchains part of Maven distribution / global toolchains
Date Sun, 19 Oct 2014 16:56:30 GMT

I think the user config has already a very big meaning because of
multiple reasons:

Typically developer workstations and CI servers all are single-user
only. So the builds are always executed with the same user. So there is
nobody complayning if the system is not configured on a system level.
This is especially true as people stay away from modifying system
config files if they are part of the software distribution and get

This is (in my thinking) the main reason why the focus on ~/.m2.
However of course I would agree the configuration is symmetric, so it
should also look for a system wide toolchain file.

BTW: I see there another problem. Toolchains are seldomly used. There
is still a lot of dicussions on enforcers/source/target versions.
Having a toolchain declaration would fix all of them at the same time,
so it is much preferred. Maybe all plugins should mention toolchain as
the better alternative for those parameters?

(And if would be good to actually fill the gaps on this wiki page:

Related to this, can a system dependency refer to a toolchain home?
(especially rt.jar or similiar needs).


 Am Sun, 19 Oct 2014 18:18:34 +0200
schrieb "Robert Scholte" <>:

> 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]
> ( 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:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message