geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <drw_...@yahoo.com>
Subject Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
Date Tue, 02 Jan 2007 03:13:36 GMT
Can we host a repo per release (1.2, 2.0, ...) on guild.org and only 
check-in the repo contents in svn when a branch is created, so it gets 
tagged with a release (milestone, beta, final, ...)?  That would keep us 
from bloating the storage space required in the repo due to binary diffs 
of frequently changing artifacts.

Then, we could define m2 profiles to pull the artifacts from the gbuild 
hosted repo or svn for released builds or from the public repos for 
people working on new code before it is committed and the gbuild repo 
updated.


-Donald


Jason Dillon wrote:
> Thanks Kevan for looking into this.
> 
> This is one of the big issues I have with mvn and SNAPSHOT artifacts... 
> other peoples projects can break your projects build with out any 
> notice, no change log, and in many cases hours of someone debugging a 
> build to figure it out.
> 
> Perhaps we should simply not use *any* SNAPSHOT artifacts anymore?  And 
> only use timestamp-build artifacts when non-released (snapshot deployed) 
> artifacts need to be consumed.  The chances of those *just changing* and 
> breaking things are slimmer... though the chance of them disappearing 
> from a repo are much higher.
> 
> We could always fix that by finally setting up our own repo in svn, 
> maybe here for now:
> 
>     https://svn.apache.org/repos/asf/geronimo/repository
> 
> Might hold anywhere from 50-100 megs of artifacts to support a Geronimo 
> Server build.  And we could probably just start out with some of the 
> more risky artifacts, like this timestamp-build artifact (and move over 
> the local repos that are in the server/trunk build).
> 
> Though eventually it would be nice to simply be able to prime the local 
> repo and build offline:
> 
>     svn co https://svn.apache.org/repos/asf/geronimo/repository
>     cp -r repository/* ~/.m2/repository
>     svn co https://svn.apache.org/repos/asf/geronimo/server/trunk server
>     cd server
>     mvn -o
> 
> Though I'm not sure if the current ASF httpd config for svn.apache.org 
> will handle this well.   I know that its possible to setup httpd+svn to 
> behave optimally for this, just not sure that the ASF config asis will 
> or not.
> 
> --jason
> 
> 
> On Dec 27, 2006, at 9:33 AM, Kevan Miller wrote:
> 
>>
>> On Dec 26, 2006, at 6:55 PM, Jason Dillon wrote:
>>
>>> I've run the server/trunk build twice on JDK 1.5 twice from a clean 
>>> repo, both times it fails here:
>>>
>>> <snip>
>>> [INFO] 
>>> ----------------------------------------------------------------------------

>>>
>>> [INFO] Building Geronimo :: Service :: Builder
>>> [INFO]    task-segment: [install]
>>> [INFO] 
>>> ----------------------------------------------------------------------------

>>>
>>> [INFO] snapshot 
>>> org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for 
>>> updates from apache-snapshots
>>> [INFO] snapshot 
>>> org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for 
>>> updates from codehaus-snapshots
>>> [INFO] snapshot 
>>> org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for 
>>> updates from apache.snapshots
>>> Downloading: 
>>> http://snapshots.repository.codehaus.org/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1-SNAPSHOT/xmlbeans-maven-plugin-2.0.1-20061223.141616-9.pom

>>>
>>> 5K downloaded
>>> Downloading: 
>>> http://repository.codehaus.org/org/codehaus/mojo/mojo/11/mojo-11.pom
>>> 7K downloaded
>>> Downloading: 
>>> http://snapshots.repository.codehaus.org/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1-SNAPSHOT/xmlbeans-maven-plugin-2.0.1-20061223.141616-9.jar

>>>
>>> 30K downloaded
>>> [INFO] [tools:require-java-version {execution: validate-java-version}]
>>> [INFO] [xmlbeans:xmlbeans {execution: default}]
>>> [INFO] 
>>> ------------------------------------------------------------------------
>>> [ERROR] FATAL ERROR
>>> [INFO] 
>>> ------------------------------------------------------------------------
>>> [INFO] javax/xml/stream/XMLStreamException
>>> [INFO] 
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
>>>     at java.lang.Class.getDeclaredMethods0(Native Method)
>>>     at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
>>>     at java.lang.Class.getMethod0(Class.java:2642)
>>>     at java.lang.Class.getMethod(Class.java:1579)
>>>     at org.apache.xmlbeans.XmlBeans.buildMethod(XmlBeans.java:174)
>>>     at org.apache.xmlbeans.XmlBeans.buildNodeMethod(XmlBeans.java:195)
>>>     at 
>>> org.apache.xmlbeans.XmlBeans.buildNodeToCursorMethod(XmlBeans.java:232)
>>>     at org.apache.xmlbeans.XmlBeans.(XmlBeans.java:131)
>>>     at 
>>> org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.(SchemaTypeLoaderBase.java:64)

>>>
>>>     at 
>>> org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1063)

>>>
>>>     at 
>>> org.codehaus.mojo.xmlbeans.AbstractXmlBeansPlugin.execute(AbstractXmlBeansPlugin.java:270)

>>>
>>>     at 
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)

>>>
>>>     at 
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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(DelegatingMethodAccessorImpl.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)
>>> </snip>
>>
>> I get the same error trying to build openejb/trunk/openejb2.
>>
>> I see there's a recently updated maven plugin that is likely to be the 
>> cause (or at least related). I'm picking up the following snapshot 
>> when I build:
>>
>> Downloading: 
>> http://snapshots.repository.codehaus.org/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1-SNAPSHOT/xmlbeans-maven-plugin-2.0.1-20061223.141616-9.jar

>>
>>
>> Matt says that his build works by setting the version for the plugin 
>> to <version>2.0.1-20060627.031204-7</version>
>>
>> --kevan
> 
> 
> 

Mime
View raw message