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
Hi,
first dont use "maven --version" as command cause maven will be called
by: "mvn --version" instead...
Furthermore you should not use MAVEN_HOME environment variable...only
add the bin folder of the distribution (apache-maven-3.3.3/bin) to the
PATH of your windows system
Don't
The Apache Maven team is pleased to announce the release of the
Apache Maven Shared Component: Maven Shared Utils Version 3.0.0.
This project aims to be a functional replacement for plexus-utils in Maven. It
is not a 100% API compatible replacement though but a replacement with
improvements: lots
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
I have always used MAVEN_HOME and added it to the path.
When I switch Maven versions it is easier to find the Environment
variable rather than looking through several hundred characters in PATH.
Same for all of the other software.
Makes PATH a lot shorter and easier to read.
Any reason why you
Hi Christopher
better to follow Karl Heinz advice, than downgrade. If you still see the
issue, ping this list.
I have maven 3.3.x running for months smoothly
-Dan
On Thu, Oct 15, 2015 at 9:33 PM, Cai Black
wrote:
> Thanks to everyone.
>
> Downgrading to Maven
Thanks to everyone.
Downgrading to Maven 3.2.5 resolved the issue.
Christopher (Cai) Black
Mgr. Software Development
RigNet
1880 S. Dairy Ashford, Suite 300 | Houston, TX 77077- 4760 | USA
Tel: +1.281.674.0717 | Mobile: +1.832.439.8134 | Fax: +1.281.674.0101
Email: christopher.bl...@rig.net
[RESOLVED] OK, so, apparently this is an issue with Maven 3.3.3, and when I
downgraded to Maven 3.2.5, everything worked as expected.
Christopher (Cai) Black
Mgr. Software Development
RigNet
1880 S. Dairy Ashford, Suite 300 | Houston, TX 77077- 4760 | USA
Tel: +1.281.674.0717 | Mobile:
I have 3.1.1 also working.
On Oct 15, 2015 3:45 PM, "Cai Black" wrote:
> [RESOLVED] OK, so, apparently this is an issue with Maven 3.3.3, and when
> I downgraded to Maven 3.2.5, everything worked as expected.
>
> Christopher (Cai) Black
> Mgr. Software Development
>
>