Op Sun, 02 Nov 2014 21:52:07 +0100 schreef Hervé BOUTEMY
herve.bout...@free.fr:
Le samedi 1 novembre 2014 20:52:56 Robert Scholte a écrit :
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Le samedi 1 novembre 2014 20:52:56 Robert Scholte a écrit :
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xml is quite easy: all complex types have a key,
which is
Op Sun, 19 Oct 2014 20:19:07 +0200 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
On 10/19/14 7:25 PM, Robert Scholte wrote:
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
this makes me have another idea:
why are toolchains configured in a specific toolchains.xml file instead as
settings.xml?
Regards,
Hervé
Le samedi 1 novembre 2014 15:53:16 Robert Scholte a écrit :
Op Sun, 19 Oct 2014 20:19:07 +0200 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
Very interesting suggestion.
And it shouldn't be a problem since the settings.xml is a Maven specific
file (unlike the pom.xml).
Robert
Op Sat, 01 Nov 2014 16:02:02 +0100 schreef Hervé BOUTEMY
herve.bout...@free.fr:
this makes me have another idea:
why are toolchains configured in a
Hello,
i can see advantage and disadvantage to having it in the settings file.
In my case I have multiple settings files for different repo and
security settings but only one toolchain describes the host
installed software.
One option would be to allow includes in the settings.xml, then you can
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xml is quite easy: all complex types have a key,
which is used to merge.
The toolchain entries don't have such an
Is this something we could back port to 3.0.6?
On 1 November 2014 19:52, Robert Scholte rfscho...@apache.org wrote:
Hi,
I've been working on the merger for Toolchains and my conclusion is that
we shouldn't add it to the settings.xml like it is specified right now.
Merging the settings.xml
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
Hello,
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
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
Hi,
On 10/19/14 7:25 PM, Robert Scholte wrote:
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.
That's exactly the
12 matches
Mail list logo
