You are right - that won't change much:-) Seeing a different error now:
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Unresolved compilation problem:
schemaorg_apache_xmlbeans.system.s0B2C6F16DB8124A722ED70C47675C78C
canno
t be resolved
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.Error: Unresolved compilation problem:
schemaorg_apache_xmlbeans.system.s0B2C6F16DB8124A722ED70C47675C78C
canno
t be resolved
at
org.apache.geronimo.deployment.xbeans.EnvironmentDocument.<clinit>(En
vironmentDocument.java:19)
at
org.apache.geronimo.deployment.service.EnvironmentBuilder.<clinit>(En
vironmentBuilder.java:51)
at
org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.mergeEnvironme
nt(PlanProcessorMojo.java:181)
at
org.apache.geronimo.mavenplugins.car.PlanProcessorMojo.doExecute(Plan
ProcessorMojo.java:134)
at
org.apache.geronimo.genesis.MojoSupport.execute(MojoSupport.java:122)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
any ideas?
Lin
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacek
Laskowski
Sent: Tuesday, February 06, 2007 4:06 PM
To: dev@geronimo.apache.org
Subject: Re: anyone able to build geronimo with test/itest turned on
On 2/6/07, Lin Sun <[EMAIL PROTECTED]> wrote:
> Hi there, for the past few times, I didn't have any luck in building
> Geronimo using just mvn or mvn install. I had to use
> '-Dmaven.test.skip=true -Dmaven.itest.skip=true' to skip both the test and
> itest. This is the latest error I saw when I forgot to turn off the
> test/itest.:-)
You're not alone, but I don't think it'lll change your developer's
life much ;-) Thanks for sharing the tip with
'-Dmaven.test.skip=true', though. I completely forgot about it.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
