Well, it is obviously a bug in the Alpha JVM. The default JVM is the
fast one which is known to have some problems with native code (ie.
the code that access the file system to find jars and other useful
things). So by setting MAVEN_OPTS to -Xmx256mb -classic, I can force
the JVM into classic
I was premature in my report. Maven still doesn't run on Alpha. I've
tracked the problem down to the maven-xdoc-plugin-1.4/plugin.jelly when
it tries to register a report using the attainGoal
name=${report}:register
I suspect the problem is something similar to junit class loading issue
What version of the JVM were you using?
I've currently using 1.4.1-1 but I believe I have access to other
versions which I will be trying today and reporting on.
I don't have the option to move to Linux for this process.
Jake Ewerdt wrote:
I had exactly the same problem with Maven (1.0-rc1)
The 1.3.1 version included with Tru64 in the /usr/java1.3 directory.
java version 1.3.1
Java(TM) 2 Runtime Environment, Standard Edition
Fast VM (build 1.3.1-6, native threads, mixed mode, precompiled rt.jar,
07/14/2003-13:20)
On Friday 09 January 2004 09:18 am, Erik Husby wrote:
What version
I've installed Maven-1.0-RC1 on my Windows XP system and my Alpha using
Compaq Tru64 UNIX V5.1B (Rev. 2650);
Using a shared drive, if I build the project on the Windows XP system,
it works fine. But if I build, using the same set of files on the Unix
box, Maven fails to load the JUnitTask as
I had exactly the same problem with Maven (1.0-rc1) and Tru64. I could run
all ant tasks but no ant-optional tasks (junit, chown, replaceregexp, ...).
I tried with ant 1.5.4 and 1.6. Spent a day or so trying to get it to work,
and eventually gave up and moved everything over to Linux where
