Downloading all the jars can take a while - even checking on the
SNAPSHOT jars to see if they've changed can take a while.
If you type "maven -o " it doesn't try to download the jars; so
typically works a fair bit quicker.
James
On 17 Feb 2006, at 02:49, Li, Fan wrote:
I just downloaded the latest SNAPSHOT and M4 version, both are
building successfully. For future reference, how long does the
build process normally take, assuming I already have most depended
jars in the maven repository. When I was having problem with the
build earlier, it usually takes close to an hour, now it takes less
than 10 min with tests.
Thanks
Fan
-----Original Message-----
From: Fritz Oconer [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 16, 2006 5:58 PM
To: [email protected]
Subject: Re: Build Problem
Hi Li,
There's also an option in maven where you can disable running the
unit test.
Execute the command in activemq home directory "maven -
Dmaven.test.skip=true". Can we also have a copy of the maven build
log file? this may provide information why the test-reports are not
generated. The log file can be created by adding additional
statement in the build command. e.g "maven > build.log".
Hope this helps,
Fritz
----- Original Message -----
From: "Li, Fan" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, February 17, 2006 5:08 AM
Subject: RE: Build Problem
I did not find any occurrence of '[ERROR]' in my activemq directory
after
a build fail, although there are some occurrence of 'ERROR', none
of them was in one of the /target/test-reports/TEST-$name.txt
files. My platform is RedHat Linux 7.2
Thanks
Fan
-----Original Message-----
From: James Strachan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 16, 2006 11:17 AM
To: [email protected]
Subject: Re: Build Problem
That indicates there were some JUnit test failures. We have some
tests
that fail on some platforms with timing issues; its amazingly hard
to write highly asynchronous & concurrent message based unit test
cases that always work on every platform.
If you seach for [ERROR] you'll find the actual tests that failed.
Then if
you look in "target/test-reports/TEST-$name.txt" (in the module
thats being
built) you'll find the output of the test case. If you could post
those
it'd really help us fix it.
James
On 2/16/06, Li, Fan <[EMAIL PROTECTED]> wrote:
I have been trying to build the latest source code with maven 1.0.2
and kept getting build failure. This is the build for the latest
SNAPSHOT. I am not sure if anyone had similar problem.
BUILD FAILED
File...... /home/fanli/.maven/cache/maven-multiproject-plugin-1.3.1
/plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
Unable to obtain goal [test:test] --
/home/fanli/.maven/cache/maven-test-plugin-
1.6.2/plugin.jelly:181:54: <fail> There were test failures.
Total time: 58 minutes 22 seconds
Finished at: Thu Feb 16 09:49:19 PST 2006
Thanks
Fan
--
James
-------
http://radio.weblogs.com/0112098/
James
-------
http://radio.weblogs.com/0112098/
