Re: trunk build failure
I just refreshed my Axis2 trunk and looks like they commented out this entire method processHTTPGetRequest in Axis2 trunk just this morning! Do you want to comment out this also in trunk before we work out a fix? In geronimo/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java: change // deal with GET request boolean processed = HTTPTransportUtils.processHTTPGetRequest( msgContext, response.getOutputStream(), soapAction, path, configurationContext, HTTPTransportReceiver.getGetRequestParameters(path)); to boolean processed = false; Lin Joe Bohn wrote: I'm now seeing a different build failure on trunk when building from a clean local repo. This is when building the module for geronimo-axis2. [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/bohn/geronimo/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[358,50] cannot find symbol symbol : method processHTTPGetRequest(org.apache.axis2.context.MessageContext,java.io.OutputStream,java.lang.String,java.lang.String,org.apache.axis2.context.ConfigurationContext,java.util.Map) location: class org.apache.axis2.transport.http.HTTPTransportUtils
Re: trunk build failure
Getting the same error Thanks, Tim McConnell Joe Bohn wrote: I'm now seeing a different build failure on trunk when building from a clean local repo. This is when building the module for geronimo-axis2. [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure /Users/bohn/geronimo/modules/geronimo-axis2/src/main/java/org/apache/geronimo/axis2/Axis2WebServiceContainer.java:[358,50] cannot find symbol symbol : method processHTTPGetRequest(org.apache.axis2.context.MessageContext,java.io.OutputStream,java.lang.String,java.lang.String,org.apache.axis2.context.ConfigurationContext,java.util.Map) location: class org.apache.axis2.transport.http.HTTPTransportUtils
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
On Feb 6, 2007, at 5:06 AM, anita kulshreshtha wrote: --- Jacek Laskowski <[EMAIL PROTECTED]> wrote: On 2/6/07, anita kulshreshtha <[EMAIL PROTECTED]> wrote: This will introduce cyclic dependency between openejb and geronimo build. David B. had an alternate solution. Does it mean that M2 is not able to handle cyclic dependency in a satisfactory manner? I have not tried this to give a definite answer.. The only situation where one would see the effects of this are during an offline build of geronimo and openejb from a clean repo. One must build geronimo until the build fails for openejb, then build openejb and then continue with rest of the geronimo build. The really big issue is at release time, it's an absolute nightmare. The worst. This is a problem that has frustrated everyone and is one of the things we really focused on and fixed in OpenEJB 3 and the new integration (hallelujah!). Here's an email from the not to distant past. http://mail-archives.apache.org/mod_mbox/geronimo-dev/200612.mbox/% [EMAIL PROTECTED] -David I saw the comment of Dave B. where he had said that there should've been more exclude's in OpenEJB's poms. When I compiled OE3 yesterday, I noticed lots of libs of Geronimo from past releases and thought to get rid of them, but didn't have time. I'm investigating it now. Compiling openejb with 1.2-beta is working satisfactorily. the configs and hence assembled servers do not use any 1.2-beta jars. We can continue to do the same as long as it compiles with 1.2-beta. The exclusions do _confuse_ maven about which version of openejb specs to use. The results are different from top, 'modules' and 'geronimo-openejb-builder' directory! Now geronimo and openejb use same version of openejb spec hence this problem is not there. Thanks Anita Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl __ __ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
Why isn't axis using the normal apache snapshot repo? It really sucks to have to add new repos to pick up a small set of artifacts... especially when that repo starts to cause transient build failures... :-( --jason On Feb 6, 2007, at 10:34 AM, Lin Sun wrote: This is avail here - http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-jaxws- api/SNAP SHOT/ And the ws.zones.apache.org repo is specified in root pom.xml: axis2-m2-repo Axis2 M2 Repository http://ws.zones.apache.org/repository2/ default true true Could this be a network glitch? Lin -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 11:13 AM To: [email protected] Subject: Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code I finally got past the geronimo-openejb-builder failure using OpenEJB3 Rev504103 and Server Rev504171, but now I'm seeing a failure in "Building Geronimo :: JAXWS" Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jax ws-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0- SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot- repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot- repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -Donald Sachin Patel wrote: I just hit this as well. -sachin On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - [INFO] [compiler:compile] Compiling 7 source files to E:\g20\server\modules\geronimo-openejb-builder\target\classes [INFO] --- [ERROR] BUILD FAILURE [INFO] --- [INFO] Compilation failure E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol symbol : class Cmp2Builder location: package org.apache.openejb.assembler.classic E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder -Donald
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
Yep, it took several build attempts to get all of the needed files from ws.zones.apache.org -Donald Lin Sun wrote: This is avail here - http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-jaxws-api/SNAP SHOT/ And the ws.zones.apache.org repo is specified in root pom.xml: axis2-m2-repo Axis2 M2 Repository http://ws.zones.apache.org/repository2/ default true true Could this be a network glitch? Lin -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 11:13 AM To: [email protected] Subject: Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code I finally got past the geronimo-openejb-builder failure using OpenEJB3 Rev504103 and Server Rev504171, but now I'm seeing a failure in "Building Geronimo :: JAXWS" Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jax ws-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -Donald Sachin Patel wrote: I just hit this as well. -sachin On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - [INFO] [compiler:compile] Compiling 7 source files to E:\g20\server\modules\geronimo-openejb-builder\target\classes [INFO] --- [ERROR] BUILD FAILURE [INFO] --- [INFO] Compilation failure E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol symbol : class Cmp2Builder location: package org.apache.openejb.assembler.classic E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder -Donald smime.p7s Description: S/MIME Cryptographic Signature
RE: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
This is avail here - http://ws.zones.apache.org/repository2/org/apache/axis2/axis2-jaxws-api/SNAP SHOT/ And the ws.zones.apache.org repo is specified in root pom.xml: axis2-m2-repo Axis2 M2 Repository http://ws.zones.apache.org/repository2/ default true true Could this be a network glitch? Lin -Original Message- From: Donald Woods [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 11:13 AM To: [email protected] Subject: Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code I finally got past the geronimo-openejb-builder failure using OpenEJB3 Rev504103 and Server Rev504171, but now I'm seeing a failure in "Building Geronimo :: JAXWS" Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jax ws-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -Donald Sachin Patel wrote: > I just hit this as well. > > -sachin > > > On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: > >> I can't get the Server trunk Rev503689 to build against a local build >> of the latest OpenEJB3 code at Rev503514. Also noticed, that the >> OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead >> of 2.0-M2 or 2.0-SNAPSHOT - >> >> [INFO] [compiler:compile] >> Compiling 7 source files to >> E:\g20\server\modules\geronimo-openejb-builder\target\classes >> [INFO] >> --- >> [ERROR] BUILD FAILURE >> [INFO] >> --- >> [INFO] Compilation failure >> E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo >> \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol >> symbol : class Cmp2Builder >> location: package org.apache.openejb.assembler.classic >> E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo >> \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol >> symbol : class Cmp2Builder >> location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder >> E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\gero nimo >> \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol >> symbol : class Cmp2Builder >> location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder >> >> >> -Donald >
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
You can download following files from "http://people.apache.org/repo/m1-snapshot-repository/org.apache.axis2/jars/"; and store in local repo ".m2/repository/org/apache/axis2/axis2-jaxws-api/SNAPSHOT": _ bytes | name _ 35,366 axis2-jaxws-api-SNAPSHOT.jar 13,383 axis2-jaxws-api-SNAPSHOT.pom 171 maven-metadata-apache-snapshots.xml 171 maven-metadata-apache.snapshots.xml 171 maven-metadata-codehaus-snapshots.xml 171 maven-metadata-maven-repo1.xml 171 maven-metadata-ws-zones.xml - A Fei - From: Donald Woods <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code Date: Tue, 06 Feb 2007 11:12:46 -0500 I finally got past the geronimo-openejb-builder failure using OpenEJB3 Rev504103 and Server Rev504171, but now I'm seeing a failure in "Building Geronimo :: JAXWS" Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jax ws-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -Donald Sachin Patel wrote: I just hit this as well. -sachin On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - [INFO] [compiler:compile] Compiling 7 source files to E:\g20\server\modules\geronimo-openejb-builder\target\classes [INFO] --- [ERROR] BUILD FAILURE [INFO] --- [INFO] Compilation failure E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol symbol : class Cmp2Builder location: package org.apache.openejb.assembler.classic E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder -Donald << smime.p7s >> _ Don't just search. Find. Check out the new MSN Search! http://search.msn.com/
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
I finally got past the geronimo-openejb-builder failure using OpenEJB3 Rev504103 and Server Rev504171, but now I'm seeing a failure in "Building Geronimo :: JAXWS" Downloading: http://people.apache.org/repo/m2-snapshot-repository/org/apache/axi s2/axis2-jaxws-api/SNAPSHOT/axis2-jaxws-api-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://people .apache.org/repo/m2-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jax ws-api \ -Dversion=SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT 2) org.apache.axis2:axis2-jaxws-api:jar:SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-jaxws:jar:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus (http://repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), axis2-m2-repo (http://ws.zones.apache.org/repository2/), tomcat-m2-repo (http://tomcat.apache.org/dev/dist/m2-repository/) -Donald Sachin Patel wrote: I just hit this as well. -sachin On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - [INFO] [compiler:compile] Compiling 7 source files to E:\g20\server\modules\geronimo-openejb-builder\target\classes [INFO] --- [ERROR] BUILD FAILURE [INFO] --- [INFO] Compilation failure E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol symbol : class Cmp2Builder location: package org.apache.openejb.assembler.classic E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org\apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder -Donald smime.p7s Description: S/MIME Cryptographic Signature
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
I just hit this as well. -sachin On Feb 5, 2007, at 5:30 PM, Donald Woods wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - [INFO] [compiler:compile] Compiling 7 source files to E:\g20\server\modules\geronimo-openejb- builder\target\classes [INFO] -- - [ERROR] BUILD FAILURE [INFO] -- - [INFO] Compilation failure E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[74,44] cannot find symbol symbol : class Cmp2Builder location: package org.apache.openejb.assembler.classic E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,8] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder E:\g20\server\modules\geronimo-openejb-builder\src\main\java\org \apache\geronimo \openejb\deployment\EjbModuleBuilder.java:[359,38] cannot find symbol symbol : class Cmp2Builder location: class org.apache.geronimo.openejb.deployment.EjbModuleBuilder -Donald
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On 2/6/07, anita kulshreshtha <[EMAIL PROTECTED]> wrote: > > This will introduce cyclic dependency between openejb and geronimo > > build. David B. had an alternate solution. > > Does it mean that M2 is not able to handle cyclic dependency in a > satisfactory manner? I have not tried this to give a definite answer.. The only situation where one would see the effects of this are during an offline build of geronimo and openejb from a clean repo. One must build geronimo until the build fails for openejb, then build openejb and then continue with rest of the geronimo build. > > I saw the comment of Dave B. where he had said that there should've > been more exclude's in OpenEJB's poms. When I compiled OE3 yesterday, > I noticed lots of libs of Geronimo from past releases and thought to > get rid of them, but didn't have time. I'm investigating it now. Compiling openejb with 1.2-beta is working satisfactorily. the configs and hence assembled servers do not use any 1.2-beta jars. We can continue to do the same as long as it compiles with 1.2-beta. The exclusions do _confuse_ maven about which version of openejb specs to use. The results are different from top, 'modules' and 'geronimo-openejb-builder' directory! Now geronimo and openejb use same version of openejb spec hence this problem is not there. Thanks Anita > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
On 2/6/07, anita kulshreshtha <[EMAIL PROTECTED]> wrote: This will introduce cyclic dependency between openejb and geronimo build. David B. had an alternate solution. Does it mean that M2 is not able to handle cyclic dependency in a satisfactory manner? I saw the comment of Dave B. where he had said that there should've been more exclude's in OpenEJB's poms. When I compiled OE3 yesterday, I noticed lots of libs of Geronimo from past releases and thought to get rid of them, but didn't have time. I'm investigating it now. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
This will introduce cyclic dependency between openejb and geronimo build. David B. had an alternate solution. Please see: http://www.nabble.com/Re%3A-geronimo-openejb-is-downloading-1.2-beta-jars-p8662387.html This error was reported 4 days ago! http://www.nabble.com/compilation-failure-in-geronimo-openejb-builder-tf3155507.html#a8750252 It appears spam filters are doing their job too well! Thanks Anita --- Jacek Laskowski <[EMAIL PROTECTED]> wrote: > On 2/5/07, Donald Woods <[EMAIL PROTECTED]> wrote: > > I can't get the Server trunk Rev503689 to build against a local > build of > > the latest OpenEJB3 code at Rev503514. Also noticed, that the > OpenEJB3 > > build is still using the Geronimo 1.2-beta artifacts instead of > 2.0-M2 > > or 2.0-SNAPSHOT - > > Fixed. OpenEJB 3 uses 2.0-SNAPSHOT libs of Apache Geronimo. Thanks > for > reporting! (there're still places where the previous bits are > transitively downloaded, though, but it's way to late for me to fix > it > now). > > $ svn ci -m 'Upgrade Geronimo libs to 2.0-SNAPSHOT' pom.xml > Sendingpom.xml > Transmitting file data . > Committed revision 503917. > > Jacek > > -- > Jacek Laskowski > http://www.JacekLaskowski.pl > Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
Re: Trunk build failure in geronimo-openejb-builder w/ latest OpenEJB3 code
On 2/5/07, Donald Woods <[EMAIL PROTECTED]> wrote: I can't get the Server trunk Rev503689 to build against a local build of the latest OpenEJB3 code at Rev503514. Also noticed, that the OpenEJB3 build is still using the Geronimo 1.2-beta artifacts instead of 2.0-M2 or 2.0-SNAPSHOT - Fixed. OpenEJB 3 uses 2.0-SNAPSHOT libs of Apache Geronimo. Thanks for reporting! (there're still places where the previous bits are transitively downloaded, though, but it's way to late for me to fix it now). $ svn ci -m 'Upgrade Geronimo libs to 2.0-SNAPSHOT' pom.xml Sendingpom.xml Transmitting file data . Committed revision 503917. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Trunk build failure at geronimo-axis2 module
Problem solved. Apparently deleting just o.a.g.* from the local repo wasn't enough. I had to delete org/apache/axis2 too. Cheers Prasad On 2/5/07, Prasad Kashyap <[EMAIL PROTECTED]> wrote: Revision 503718Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 503718 Node Kind: directory Schedule: normal Last Changed Author: dims Last Changed Rev: 503689 Last Changed Date: 2007-02-05 09:06:26 -0500 (Mon, 05 Feb 2007) Properties Last Updated: 2007-01-03 09:25:29 -0500 (Wed, 03 Jan 2007) /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PropertyType.java:[14,33] package javax.xml.bind.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PropertyType.java:[15,33] package javax.xml.bind.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PropertyType.java:[16,33] package javax.xml.bind.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PropertyType.java:[17,42] package javax.xml.bind.annotation. adapters does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PropertyType.java:[18,42] package javax.xml.bind.annotation. adapters does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[13,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[14,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[15,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[16,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[17,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[18,33] package javax.xml.bin d.annotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[19,42] package javax.xml.bin d.annotation.adapters does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/PersistenceContextRefType.java:[20,42] package javax.xml.bin d.annotation.adapters does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/ServletLinkType.java:[11,33] package javax.xml.bind.annotati on does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/ServletLinkType.java:[12,33] package javax.xml.bind.annotati on does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/ServletLinkType.java:[13,33] package javax.xml.bind.annotati on does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/EjbLinkType.java:[11,33] package javax.xml.bind.annotation d oes not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/EjbLinkType.java:[12,33] package javax.xml.bind.annotation d oes not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/EjbLinkType.java:[13,33] package javax.xml.bind.annotation d oes not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/EnvEntryTypeValuesType.java:[11,33] package javax.xml.bind.a nnotation does not exist /home/prasad/geronimo/trunk/modules/geronimo-axis2/src/main/generated/org/apache /axis2/jaxws/javaee/EnvEntryTypeValuesType.java:[12,33] package javax.xml.bind.a nnotation does not exist
Re: trunk build failure
Looks like I was missing some changes when I ran tools:show-
dependencies... for some reason commons-logging is being excluded. I
think this might be a bug in maven, its excluding the dep because
another module has an exclude listed.
For now we'll just add the dependency... maybe this will be fixed in
Maven 2.0.5.
--jason
On Jan 13, 2007, at 2:52 AM, Jason Dillon wrote:
On Jan 12, 2007, at 9:43 PM, Jarek Gawor wrote:
I just added a dep.on commons-logging in jetty6-builder to
temporarily
work around it. I think that dep. used to be pulled in through jetty6
through testsupport-common dep. which was recently removed.
geronimo-jetty6 was only defining the testsupport-common dependency
so that it could exclude any selenium jars (which pulled in old
versions of Jetty), since all modules pick up testsupport-common as
a test dep by default. It should have set the scope to test
though, which was why commons-logging was available to that module
with out an explicit dependency reference.
I am however surprised that JCL is not being picked up from
geronimo-kernel...
mvn -Ptools tools:show-dependencies -Dverbose=true
[INFO]
--
--
[INFO] Building Geronimo :: Jetty 6 :: Builder
[INFO]task-segment: [tools:show-dependencies]
[INFO]
--
--
[INFO] [tools:show-dependencies]
...
[INFO] org.apache.geronimo.modules:geronimo-jetty6-builder:jar
{ version=2.0-SNAPSHOT, scope=null }
[INFO] org.apache.geronimo.modules:geronimo-jetty6:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-connector:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-
security:jar { version=2.0-SNAPSHOT, scope=compile }
[INFO] activeio:activeio:jar { version=2.0-r118,
scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
jacc_1.1_spec:jar { version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-j2ee:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
ejb_2.1_spec:jar { version=1.0.1, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-common:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-naming:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
jta_1.1_spec:jar { version=1.0, scope=compile }
[INFO] org.apache.xbean:xbean-naming:jar
{ version=2.7, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-kernel:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] xstream:xstream:jar { version=1.1.3,
scope=compile }
[INFO] commons-logging:commons-logging:jar
{ version=1.0.4, scope=compile }
...
Looks like it should be included. But I've been up for too long, 4
hour delay on the flight home :-( Will double check tomorrow.
--jason
Re: trunk build failure
On Jan 12, 2007, at 9:43 PM, Jarek Gawor wrote:
I just added a dep.on commons-logging in jetty6-builder to temporarily
work around it. I think that dep. used to be pulled in through jetty6
through testsupport-common dep. which was recently removed.
geronimo-jetty6 was only defining the testsupport-common dependency
so that it could exclude any selenium jars (which pulled in old
versions of Jetty), since all modules pick up testsupport-common as a
test dep by default. It should have set the scope to test though,
which was why commons-logging was available to that module with out
an explicit dependency reference.
I am however surprised that JCL is not being picked up from geronimo-
kernel...
mvn -Ptools tools:show-dependencies -Dverbose=true
[INFO]
[INFO] Building Geronimo :: Jetty 6 :: Builder
[INFO]task-segment: [tools:show-dependencies]
[INFO]
[INFO] [tools:show-dependencies]
...
[INFO] org.apache.geronimo.modules:geronimo-jetty6-builder:jar
{ version=2.0-SNAPSHOT, scope=null }
[INFO] org.apache.geronimo.modules:geronimo-jetty6:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-connector:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-security:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] activeio:activeio:jar { version=2.0-r118,
scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
jacc_1.1_spec:jar { version=1.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-j2ee:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
ejb_2.1_spec:jar { version=1.0.1, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-common:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-naming:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] org.apache.geronimo.specs:geronimo-
jta_1.1_spec:jar { version=1.0, scope=compile }
[INFO] org.apache.xbean:xbean-naming:jar
{ version=2.7, scope=compile }
[INFO] org.apache.geronimo.modules:geronimo-kernel:jar
{ version=2.0-SNAPSHOT, scope=compile }
[INFO] xstream:xstream:jar { version=1.1.3,
scope=compile }
[INFO] commons-logging:commons-logging:jar
{ version=1.0.4, scope=compile }
...
Looks like it should be included. But I've been up for too long, 4
hour delay on the flight home :-( Will double check tomorrow.
--jason
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
On Jan 5, 2007, at 3:27 PM, David Jencks wrote: I ran into this last night and changing versions of the xmlbeans plugin had no effect for me. After some study I believe but can't yet prove that after the maven folks telling me it was absolutely impossible to fix the xmlbeans 2.0.0 pom so it was correct, it got changed to a new and differently broken form. I don't think this has anything to do with snapshots, but rather instability of the allegedly permanent non-snapshot maven repo. Does anyone know if there is a changelog for the central repo? Works for me, if i remove 2.0.1-SNAPSHOT from my local repo (i.e. rm - rf ~/.m2/repository/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1- SNAPSHOT). Well, you can use the date of the snapshot as a rough estimate of when a change was introduced. So, what do the maven folks say "we" are supposed to do about this? --kevan
Re: trunk build failure
Hello Alan, Thanks for fixing the build so quickly. I had some local changes that I was not able to commit before these Jetty6 API changes. Hopefully, I believe that the new API is now pretty stable as session migration, replication, fail-over, redistribution of session states when a JettyWebAppContext is stopped and sticky load-balancing is working OK. Thanks, Gianny On 06/01/2007, at 8:27 AM, Alan D. Cabrera wrote: On Jan 5, 2007, at 1:19 PM, Jarek Gawor wrote: Building trunk fails for me with: c:\development\geronimo\modules\geronimo-jetty6\src\main\java\org \apache\geronimo\jetty6\cluster\ClusteredSessionManager.java:[142,12] cannot find symbol symbol : constructor Session(java.lang.String) location: class org.mortbay.jetty.servlet.AbstractSessionManager.Session Jetty just changed their signature. I fixed our code. Regards, Alan
Re: trunk build failure
Builds fine now. Thanks! On 1/5/07, Alan D. Cabrera <[EMAIL PROTECTED]> wrote: On Jan 5, 2007, at 1:19 PM, Jarek Gawor wrote: > Building trunk fails for me with: > > c:\development\geronimo\modules\geronimo-jetty6\src\main\java\org > \apache\geronimo\jetty6\cluster\ClusteredSessionManager.java:[142,12] > cannot find symbol > symbol : constructor Session(java.lang.String) > location: class > org.mortbay.jetty.servlet.AbstractSessionManager.Session Jetty just changed their signature. I fixed our code. Regards, Alan
Re: trunk build failure
On Jan 5, 2007, at 1:19 PM, Jarek Gawor wrote: Building trunk fails for me with: c:\development\geronimo\modules\geronimo-jetty6\src\main\java\org \apache\geronimo\jetty6\cluster\ClusteredSessionManager.java:[142,12] cannot find symbol symbol : constructor Session(java.lang.String) location: class org.mortbay.jetty.servlet.AbstractSessionManager.Session Jetty just changed their signature. I fixed our code. Regards, Alan
Re: trunk build failure
Hi, I am fixing this problem right now. Should be fixed in about 10 minutes. Sorry for this problem. Thanks, Gianny On 06/01/2007, at 8:19 AM, Jarek Gawor wrote: Building trunk fails for me with: c:\development\geronimo\modules\geronimo-jetty6\src\main\java\org \apache\geronimo\jetty6\cluster\ClusteredSessionManager.java:[142,12] cannot find symbol symbol : constructor Session(java.lang.String) location: class org.mortbay.jetty.servlet.AbstractSessionManager.Session Jarek
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
I ran into this last night and changing versions of the xmlbeans
plugin had no effect for me.
After some study I believe but can't yet prove that after the maven
folks telling me it was absolutely impossible to fix the xmlbeans
2.0.0 pom so it was correct, it got changed to a new and differently
broken form. I don't think this has anything to do with snapshots,
but rather instability of the allegedly permanent non-snapshot maven
repo.
Does anyone know if there is a changelog for the central repo?
thanks
david jencks
On Dec 27, 2006, at 5:18 PM, 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:
[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.De
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
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:
[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(Default
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
we actually do nightly builds on ws.zones.apache.org and the snapshots are available there: ws.zones.apache.org/repository/ the snapshot jars are also ssh/copied over to people.apache.org/repo/m1-snapshot-repository/ So that makes it 2 points of failure instead of just one. We did this during the last big infra migration when mino was down for a few days I guess svk and bazaar are equivalent...easy to set up. the main thing is we can tell infra that we don't need anything backed up and even if the whole zone goes kaput the project can still go on since it is just the repo stored in svk/bazaar. When i last played with it, bazaar was very easy to setup/use and can just work off a directory (no need for a BerkleyDB instance etc..). So my 2 cents is that it will help reduce pulling jars down to local repo if we set one up. if we lose the box, we can just re-populate it from any one of the distriibuted copies... thanks, -- dims On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote: On Dec 27, 2006, at 6:05 PM, Davanum Srinivas wrote: > Example: We could host a https://geronimo.zones.apache.org/repository > there and nightlies off of continuum. Of course, #asfinfra folks won't > let us run our own svn server :) If they won't let us run our own svn server... then we loose much of the point of having our own repository. Might work to use svn.apache.org to host the binaries and then periodically export to that zone so that regular non-whacky httpd config can be used to serve it. That still assumes that the management of the binaries will work reasonably well with the whacky svn.apache.org httpd config. > How about a bazaar backed maven2 repo? (http://bazaar-vcs.org/) I've never heard of this before... but if they won't let us run a svn repo, why would they let us run one of these? How is bazaar different than svk do you know? --jason -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
On Dec 27, 2006, at 6:05 PM, Davanum Srinivas wrote: Example: We could host a https://geronimo.zones.apache.org/repository there and nightlies off of continuum. Of course, #asfinfra folks won't let us run our own svn server :) If they won't let us run our own svn server... then we loose much of the point of having our own repository. Might work to use svn.apache.org to host the binaries and then periodically export to that zone so that regular non-whacky httpd config can be used to serve it. That still assumes that the management of the binaries will work reasonably well with the whacky svn.apache.org httpd config. How about a bazaar backed maven2 repo? (http://bazaar-vcs.org/) I've never heard of this before... but if they won't let us run a svn repo, why would they let us run one of these? How is bazaar different than svk do you know? --jason
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
Example: We could host a https://geronimo.zones.apache.org/repository
there and nightlies off of continuum. Of course, #asfinfra folks won't
let us run our own svn server :)
How about a bazaar backed maven2 repo? (http://bazaar-vcs.org/)
-- dims
On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Not that I am aware of... though I'm not sure what we would do with a
zone anyways... from talking with some peeps in #infra seems like we
are really restricted to what we can run on a zone, so I don't see
the point of using it.
But maybe if we could run a simple svn server there for this repo
that would be nice... though really would want to have the same svn
repo that holds the source code to also hold this repo, so that we
can tag them together.
* * *
Why, what are you thinking the zone could be used for?
--jason
On Dec 27, 2006, at 3:50 PM, Davanum Srinivas wrote:
> Do we have a request pending for a geronimo.zones.apache.org?
>
> -- dims
>
> On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> 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:
>> >>
>> >>
>> >> [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:1
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
Not that I am aware of... though I'm not sure what we would do with a
zone anyways... from talking with some peeps in #infra seems like we
are really restricted to what we can run on a zone, so I don't see
the point of using it.
But maybe if we could run a simple svn server there for this repo
that would be nice... though really would want to have the same svn
repo that holds the source code to also hold this repo, so that we
can tag them together.
* * *
Why, what are you thinking the zone could be used for?
--jason
On Dec 27, 2006, at 3:50 PM, Davanum Srinivas wrote:
Do we have a request pending for a geronimo.zones.apache.org?
-- dims
On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> 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:
>>
>>
>> [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
>> (Abstra
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
Do we have a request pending for a geronimo.zones.apache.org?
-- dims
On 12/27/06, Jason Dillon <[EMAIL PROTECTED]> 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:
>>
>>
>> [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.executeGoalWithLi
>> fecycle(DefaultLifecycleExecutor.java:475)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
>> (DefaultLifecycleExecutor.java:454)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>> dleFailures(DefaultLifecycleExecutor.java:306)
>>
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
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:
[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.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.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
(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
I updated the project Pom to refer to the older SNAPSHOT for now.
I'll contact the XMLBeans guys to work on the issue.
On Dec 27, 2006, at 12:33 PM, 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:
[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.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.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
(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)
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 2.0.1-20060627.031204-7
--kevan
Matt Hogstrom
[EMAIL PROTECTED]
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
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:
[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.executeGoalWithLif
ecycle(DefaultLifecycleExecutor.java:475)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand
leFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment
s(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)
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 2.0.1-20060627.031204-7
--kevan
Re: trunk build failure
You have existing classes compiled that reference EDU/oswego/cs/dl/util/concurrent/Executor which is no longer used by the main codebase. mvn clean install--jasonOn Sep 13, 2006, at 10:30 AM, Sachin Patel wrote:Anyone seeing the following?[INFO] [surefire:test][INFO] Surefire report directory: /Users/sppatel/geronimo/trunk/modules/geronimo-connector/target/surefire-reportsorg.apache.maven.surefire.booter.SurefireExecutionException: EDU/oswego/cs/dl/util/concurrent/Executor; nested exception is java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/Executorjava.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/Executor at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:1655) at java.lang.Class.getMethod0(Class.java:1901) at java.lang.Class.getMethod(Class.java:984) at org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:173) at org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.java:137) at org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:244) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:101) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147) at org.apache.maven.surefire.Surefire.run(Surefire.java:108) 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:324) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)[INFO] [ERROR] BUILD FAILURE[INFO] -sachin
Re: trunk build failure
That worked, thanks Sergey. Paul On 9/13/06, Sergey Elin <[EMAIL PROTECTED]> wrote: Did you try to clean trunk via mvn clean before build? 2006/9/13, Paul McMahan <[EMAIL PROTECTED]>: > Sachin, I'm seeing that error too. > > > Paul > > > On 9/13/06, Sachin Patel <[EMAIL PROTECTED]> wrote: > > > > Anyone seeing the following? > > > > [INFO] [surefire:test] > > [INFO] Surefire report directory: > > /Users/sppatel/geronimo/trunk/modules/geronimo-connector/target/surefire-reports > > org.apache.maven.surefire.booter.SurefireExecutionException: > > EDU/oswego/cs/dl/util/concurrent/Executor; nested exception > > is java.lang.NoClassDefFoundError: > > EDU/oswego/cs/dl/util/concurrent/Executor > > java.lang.NoClassDefFoundError: > > EDU/oswego/cs/dl/util/concurrent/Executor > > at java.lang.Class.getDeclaredMethods0 (Native > > Method) > > at > > java.lang.Class.privateGetDeclaredMethods(Class.java:1655) > > at java.lang.Class.getMethod0(Class.java:1901) > > at java.lang.Class.getMethod(Class.java :984) > > at > > org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:173) > > at > > org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject (JUnitTestSet.java:137) > > at > > org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:244) > > at > > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets (AbstractDirectoryTestSuite.java:101) > > at > > org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147) > > at > > org.apache.maven.surefire.Surefire.run(Surefire.java :108) > > 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:324) > > at > > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess (SurefireBooter.java:225) > > at > > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) > > [INFO] > > > > [ERROR] BUILD FAILURE > > [INFO] > > > > > > > > > > -sachin > > > > >
Re: trunk build failure
Did you try to clean trunk via mvn clean before build?2006/9/13, Paul McMahan <[EMAIL PROTECTED]>: Sachin, I'm seeing that error too.PaulOn 9/13/06, Sachin Patel <[EMAIL PROTECTED]> wrote:>> Anyone seeing the following?>> [INFO] [surefire:test] > [INFO] Surefire report directory:> /Users/sppatel/geronimo/trunk/modules/geronimo-connector/target/surefire-reports> org.apache.maven.surefire.booter.SurefireExecutionException:> EDU/oswego/cs/dl/util/concurrent/Executor; nested exception > is java.lang.NoClassDefFoundError:> EDU/oswego/cs/dl/util/concurrent/Executor> java.lang.NoClassDefFoundError:> EDU/oswego/cs/dl/util/concurrent/Executor> at java.lang.Class.getDeclaredMethods0 (Native> Method)> at> java.lang.Class.privateGetDeclaredMethods(Class.java:1655)> at java.lang.Class.getMethod0(Class.java:1901)> at java.lang.Class.getMethod(Class.java :984)> at> org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:173)> at> org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject (JUnitTestSet.java:137)> at> org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:244)> at> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets (AbstractDirectoryTestSuite.java:101)> at> org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147)> at> org.apache.maven.surefire.Surefire.run(Surefire.java :108)> 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:324)> at> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess (SurefireBooter.java:225)> at> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747)> [INFO]> > [ERROR] BUILD FAILURE> [INFO]> -sachin>>
Re: trunk build failure
Sachin, I'm seeing that error too. Paul On 9/13/06, Sachin Patel <[EMAIL PROTECTED]> wrote: Anyone seeing the following? [INFO] [surefire:test] [INFO] Surefire report directory: /Users/sppatel/geronimo/trunk/modules/geronimo-connector/target/surefire-reports org.apache.maven.surefire.booter.SurefireExecutionException: EDU/oswego/cs/dl/util/concurrent/Executor; nested exception is java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/Executor java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/Executor at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:1655) at java.lang.Class.getMethod0(Class.java:1901) at java.lang.Class.getMethod(Class.java:984) at org.apache.maven.surefire.junit.JUnitTestSet.createInstanceFromSuiteMethod(JUnitTestSet.java:173) at org.apache.maven.surefire.junit.JUnitTestSet.constructTestObject(JUnitTestSet.java:137) at org.apache.maven.surefire.junit.JUnitTestSet.getTestCount(JUnitTestSet.java:244) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:101) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147) at org.apache.maven.surefire.Surefire.run(Surefire.java:108) 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:324) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) [INFO] [ERROR] BUILD FAILURE [INFO] -sachin
Re: trunk Build failure - can't download a lot of files
> -Original Message- > From: David Blevins [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 25, 2006 8:37 AM > To: [email protected] > Subject: Re: trunk Build failure - can't download a lot of files > > Something is preventing you from connecting to the public maven > repositories and downloading jars: "Connection timed out: connect" > is the big sign of that. > > If there is an http proxy between you and the internet, > you'll need to configure maven's proxy settings. > > -David i don't have proxy, i tried it at home. it's a direct cable connection. i have a firewall for incoming connections. maybe i should read a little bit about maven's network setups. i wonder if there's any way to download everything offline? it's very inconvinient and slow the way it is now. thanks, argyn
RE: Trunk build failure: Case-sensitive issue
I figured that the problem was in plugin.jelly file, line 99. The issue is that I put a repository path as l:/bla-bla, and in Windows it's equivalent to L:/bla-bla, but plugin.jelly thinks it's different path. argyn > -Original Message- > From: Kuketayev, Argyn (Contractor) > [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 25, 2006 10:24 AM > To: [email protected] > Subject: Trunk build failure: Case-sensitive issue > > I got this when building from the trunk: > > > ear:ear: > ear:generate-ear-descriptor: > [echo] Generating > L:\work\geronimo\geronimo\applications\console-ear/target/ > application.xml > > [echo] Building EAR geronimo-console-1.2-SNAPSHOT with > appxml "L:\work\geron > imo\geronimo\applications\console-ear/target/application.xml" > > BUILD FAILED > File.. L:\work\geronimo\geronimo\maven.xml > Element... maven:reactor > Line.. 217 > Column 158 > Unable to obtain goal [multiproject:install-callback] -- > l:\work\.maven\cache\ma > ven-ear-plugin-1.6\plugin.jelly:99:24: > Case-sensitive issue: > The depe > ndency geronimo:geronimo-console-framework has a case > problem. The dependency w as either retrieved in the past > with the wrong case or has been specified with t he wrong > case in your project.xml file. Fix your project.xml or > update your loc al repository with the properly-cased file > and try again. > Total time: 10 minutes 10 seconds > Finished at: Tue Apr 25 10:20:24 EDT 2006 > > What is it? How to fix? > > argyn >
Re: trunk Build failure - can't download a lot of files
On Apr 25, 2006, at 5:12 AM, argyn wrote: when i try to build with "maven new" command, it fails to download a lot files. apparently, iy is able to download some files. here's an example of failed download: === Attempting to download geronimo-jmxremoting-1.2-SNAPSHOT.jar. Error retrieving artifact from [http://cvs.apache.org/repository/ geronimo/jars/geronimo-jmxremoting- 1.2-SNAPSHOT.jar]: java.net.ConnectException: Connection timed out: connect Artifact /geronimo/jars/geronimo-jmxremoting-1.2-SNAPSHOT.jar doesn't exists in remote repository, b ut it exists locally == Unfortunately, some files do not exist localy, so the build fails at the end. If i build with "maven -o new" command, then it fails too. this time it can't find some files again. for example: = Copying incubator-activemq/activemq-gbean-management/4.0-SNAPSHOT/jar BUILD FAILED File.. C:\Documents and Settings\argyn\.maven\cache\geronimo- assembly-plugin-1.2.0-8\plugin.jell y Element... assemble:installConfig Line.. 190 Column 145 Dependency: incubator-activemq/activeio-core/3.0-SNAPSHOT/jar not found in local maven repo: for con figuration: geronimo/activemq-broker/1.2-SNAPSHOT/car i tried to download some of these files manually and bput in maven's cache. it worked for some. i couldn't find the above file anywhere. also, it's veru inconvinient to look up these files manually. is something wrong with my configuration? why can't it download files itself? is there any way to configure mirrors? the strange thing is that if build with "maven" command, it says that build was successfull, but them there's nothing assemblies dir, there's no /bin/server.jar file there. Something is preventing you from connecting to the public maven repositories and downloading jars: "Connection timed out: connect" is the big sign of that. If there is an http proxy between you and the internet, you'll need to configure maven's proxy settings. -David
