Thanks for the help Brett. Damn those (case)insensitive file systems :)
Is it possible to see more info in the zones than the build-log itself?
It would be helpful in cases like this one to be able to see the reports
generated by surefire.
--
Dennis Lundberg
Brett Porter wrote:
The zones are solaris x86 machines. It uses the Maven bootstrap (so the
version used is the version built). JDK 1.4.2.
I've fixed it - same problem occured on Linux. The files were added as
PCCSureFire... but referenced as PCCSurefire... (not caps). This works
on Windows because filenames are case-insensitive.
I'm a Windows user too so I wasn't seeing it - I highly recommend
grabbing yourself VMWare server so you've got a Linux installation on
hand :)
We can give out access to the Maven zone as well (though it's not really
conducive to debugging there - we really should be moving away from ci
and towards using Continuum to run all these tests).
Cheers,
Brett
On 22/07/2006 9:30 AM, Dennis Lundberg wrote:
Brett Porter wrote:
This is the model converter tests failing. Any ideas?
- Brett
On 21/07/2006 9:33 AM, [EMAIL PROTECTED] wrote:
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060720.233000.txt
I've been going through this over and over and I am unable to
reproduce these errors locally (WinXP, Sun JDK 1.4.2_11). How are
"zones" set up? What version of Maven is used to build? Locally I have
tried using Maven 2.0.4 and 2.0.5-SNAPSHOT to build both trunk and
maven-2.0.x branch of components.
On trunk the reactor build fails in maven-embedder and model-converter
only build works without test errors.
On maven-2.0.x branch reactor build succeeds as well as
model-converter only.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]