Hello Chad,
I think the behavior is the same, here's what I did:
* I built multi-module project with mvn clean install - now all artifact
are in my local repository.
* I changed directory to the top-level module, which depends on other
modules in the project and executed mvn clean install -U -
If you run 'mvn -v' you should see the JDK version used by Maven.
The easiest way to change this is to adjust the JAVA_HOME environment
variable.
-Robert
Op Sat, 14 Jul 2012 06:09:24 +0200 schreef larmbr nasa4...@gmail.com:
I am running the netty project.
when i run mvn clean install
It
Sir
Thanks for your reply
as you suggest that galileo is an old version that means it is not capable
to install maven plugin???
On Thu, Jul 12, 2012 at 10:48 PM, Jörg Schaible joerg.schai...@gmx.dewrote:
Galileo is simply too old. JDT 3.6 is at least Helios. Consider using a
newer version of
The solution is to use a junit assumption to skip the test, e.g.
Assume.assumeThat(Test fails on windows,
System.getProperty(file.seperator.char), is(/));
Added to the start of each test method will cause them to be skipped on windows
but run elsewhere...
Note I am on my phone and memory is
1. What does the maven-surefire-plugin exactly do? It still fails, but
not so much like without it.
You were already using Surefire, you just had not declared a specific
version of the plugin to use, so you were probably using an earlier
version that might have had a bug which is resolved in
as you suggest that galileo is an old version that means it is not capable
to install maven plugin???
Yes, this is what he said. Upgrade your Eclipse.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
