I think that we have been using Maven since 2007-2008 and it has not
caused a problem but I was wondering if we had just been lucky.
We almost always use it from inside Eclipse/STS so that adds a layer of
protection (or obscurity).
In the Eclipse preferences, we do override the Eclipse built-in Maven
installation location with the location of the one (latest) that we
download and install separately.
From your comment, it could be that Eclipse overrides the Widows
definition of MAVEN_HOME with its Maven settings.
Thanks for the clarification.
Still learning something new every day!
Ron
On 15/10/2015 5:13 PM, [email protected] wrote:
Hello Ron,
As far as I understand it maven uses MAVEN_HOME internally. However it will
deduce and then overwrite the value based on the scripts execution path. So it
can be pretty confusing when the PATH finds one version and you MAVEN_HOME
points to another. If both agree, then there is no problem to use it (although
its not documented to be a possible external config).
(Having said that, I am not sure if things changed since .mvn/ was added to
the mix. I do think maven-invoker is overwriting it, so at least child mavens
are robust against a (wrong) HOME).
Gruss
Bernd
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
