[BUILD] trunk: Failed for Revision: 937757
Geronimo Revision: 937757 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/unit-test-reports Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus
[BUILD] trunk: Failed for Revision: 937793
Geronimo Revision: 937793 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/unit-test-reports Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus
Re: [VOTE] Yoko 1.1 with osgi
Um, here's my +1 david jencks On Apr 22, 2010, at 7:38 PM, David Jencks wrote: Please vote on yoko 1.1, yoko with osgi support. It works enough so an ORB and HandleDelegate can be bound in jndi. There are no non-classloading related code changes from previous yoko releases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-013/ Tag: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.1/ Vote open for 72 hours thanks david jencks
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
+1 I checked that all the source-release tar.gz's compile and that geronimo runs with them. thanks david jencks On Apr 22, 2010, at 5:07 AM, Rick McGuire wrote: To support the upcoming Geronimo milestone release, I would like to release Java EE 6 versions of the geronimo specifications. This is a single vote for all specs new or updated for Java EE 6. In addition, the specs have been updated with common support for OSGi interactions. The RAT and IANAL plugins have been run against of the projects. All non-beta specs have clean TCK signature tests. All tag svn versions have been successfully built. Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ Unless noted, the source repos are relative to location https://svn.apache.org/repos/asf/geronimo/specs/tags/ and have the same final element as the artifact name. I am not listing each location individually because the mailing list server rejected my original email as spam because of the large number of links in the email. I apologize for the incovenience. The following specs are being voted on geronimo-activation_1.1_spec-1.1 geronimo-annotation_1.1_spec-1.0 geronimo-atinject_1.0_spec-1.0 geronimo-ejb_3.1_spec-1.0 geronimo-el_2.2_spec-1.0 geronimo-interceptor_1.1_spec-1.0 geronimo-j2ee-connector_1.6_spec-1.0 geronimo-jacc_1.4_spec-1.0 geronimo-jaspic_1.0_spec-1.1 geronimo-javaee-deployment_1.1MR3_spec-1.0.1 geronimo-javamail_1.4_spec-1.7 and the closely associated provider and uber jar releases. geronimo-javamail_1.4-1.8 Source location: geronimo/javamail/tags/geronimo-javamail_1.4-1.8 geronimo-jaxb_2.2_spec-1.0 geronimo-jaxr_1.0_spec-2.1 geronimo-jaxrpc_1.1_spec-2.1 geronimo-jaxrs_1.1_spec-1.0 geronimo-jaxws_2.2_spec-1.0 geronimo-jcdi_1.0_spec-1.0 geronimo-jpa_2.0_spec-1.1 geronimo-jsp_2.2_spec-1.0 geronimo-osgi-support-1.0 geronimo-saaj_1.3_spec-1.1 geronimo-servlet_3.0_spec-1.0 geronimo-stax-api_1.2_spec-1.0 geronimo-validation_1.0_spec-1.1 geronimo-ws-metadata_2.0_spec-1.1.3 geronimo-ccpp_1.0_spec-1.0-beta (this is a beta version that has not been verified via TCK yet)
Re: [VOTE] Yoko 1.1 with osgi
I'm seeing one blocker issue -- all of the checksums that I have downloaded do not match the corresponding checksums that I compute. For instance: $ md5sum yoko-1.1-source-release.tar.gz ; cat yoko-1.1-source-release.tar.gz.md5 md5sum yoko-1.1-source-release.tar.gz ; cat yoko-1.1-source-release.tar.gz.md5 f9283f77a4dfbfa483a085fb073bc3f7 yoko-1.1-source-release.tar.gz e849d7acbeafe1726252619e651f534c Until these are fixed, I'm -1 for the release. I'm ok with the vote proceeding, if these can be fixed in place (it doesn't look like the release artifacts need to be updated, just the checksums). There's one minor issue in the NOTICE file. The COPYRIGHT date has not been updated: Copyright 1999-2008 The Apache Software Foundation Our convention has been to keep the last year up to date, upon the release. This is not a requirement... --kevan On Apr 22, 2010, at 10:38 PM, David Jencks wrote: Please vote on yoko 1.1, yoko with osgi support. It works enough so an ORB and HandleDelegate can be bound in jndi. There are no non-classloading related code changes from previous yoko releases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-013/ Tag: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.1/
[BUILD] trunk: Failed for Revision: 937856
Geronimo Revision: 937856 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/unit-test-reports Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
On Apr 22, 2010, at 3:43 PM, Donald Woods wrote: Here are 3 scripts attached to help checkout, rat:check and build the tags in the vote. Thanks for the scripts. A few comments: 1) We are voting on source artifacts, not svn. So, I use wget. (e.g. 'wget --no-check-certificate https://repository.apache.org/content/repositories/orgapachegeronimo-007/org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.1/geronimo-activation_1.1_spec-1.1-source-release.tar.gz). 2) I generally try to insure that the svn tag is equivalent to the source archive (e.g. 'diff -r --strip-trailing-cr geronimo-activation_1.1_spec-1.1 geronimo-activation_1.1_spec-svn') SVN's handling of $Date tags can make this a bit painful... 3) Easier to use 'svn export' rather than 'svn co' 4) I generally try to verify the signatures and checksums also. --kevan
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
On Apr 22, 2010, at 3:43 PM, Donald Woods wrote: Can we ignore the following rat:check failures? geronimo-servlet_3.0_spec-1.0 - src/main/resources/javax/servlet/resources/xml.xsd src/main/resources/javax/servlet/resources/XMLSchema.dtd geronimo-javamail_1.4_spec-1.7 - src/test/resources/wmtom.bin geronimo-javamail_1.4-1.8/geronimo-javamail_1.4_provider - Several files under - src/main/resources/OSGI-INF/providers/ All look fine to me... --kevan
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
Looks good. Thanks Rick! Here's my +1 --kevan On Apr 22, 2010, at 8:07 AM, Rick McGuire wrote: To support the upcoming Geronimo milestone release, I would like to release Java EE 6 versions of the geronimo specifications. This is a single vote for all specs new or updated for Java EE 6. In addition, the specs have been updated with common support for OSGi interactions. The RAT and IANAL plugins have been run against of the projects. All non-beta specs have clean TCK signature tests. All tag svn versions have been successfully built. Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ Unless noted, the source repos are relative to location https://svn.apache.org/repos/asf/geronimo/specs/tags/ and have the same final element as the artifact name. I am not listing each location individually because the mailing list server rejected my original email as spam because of the large number of links in the email. I apologize for the incovenience. The following specs are being voted on geronimo-activation_1.1_spec-1.1 geronimo-annotation_1.1_spec-1.0 geronimo-atinject_1.0_spec-1.0 geronimo-ejb_3.1_spec-1.0 geronimo-el_2.2_spec-1.0 geronimo-interceptor_1.1_spec-1.0 geronimo-j2ee-connector_1.6_spec-1.0 geronimo-jacc_1.4_spec-1.0 geronimo-jaspic_1.0_spec-1.1 geronimo-javaee-deployment_1.1MR3_spec-1.0.1 geronimo-javamail_1.4_spec-1.7 and the closely associated provider and uber jar releases. geronimo-javamail_1.4-1.8 Source location: geronimo/javamail/tags/geronimo-javamail_1.4-1.8 geronimo-jaxb_2.2_spec-1.0 geronimo-jaxr_1.0_spec-2.1 geronimo-jaxrpc_1.1_spec-2.1 geronimo-jaxrs_1.1_spec-1.0 geronimo-jaxws_2.2_spec-1.0 geronimo-jcdi_1.0_spec-1.0 geronimo-jpa_2.0_spec-1.1 geronimo-jsp_2.2_spec-1.0 geronimo-osgi-support-1.0 geronimo-saaj_1.3_spec-1.1 geronimo-servlet_3.0_spec-1.0 geronimo-stax-api_1.2_spec-1.0 geronimo-validation_1.0_spec-1.1 geronimo-ws-metadata_2.0_spec-1.1.3 geronimo-ccpp_1.0_spec-1.0-beta (this is a beta version that has not been verified via TCK yet)
[RESULT][VOTE] Geronimo Eclipse Plugin 2.1.5 RC1
Delos, For scanning mailing list history, it's helpful if you update the Subject with a [RESULT] --kevan On Apr 23, 2010, at 3:54 AM, Delos wrote: Besides, we also get +1 from Ashish and Forrest, thanks! 2010/4/23 Delos dait...@gmail.com GEP RC1 passed the voting with following result 0: no +1: Donald, Kevan,Ivan -1: no The release process will proceed. Thank you! 2010/4/23 Forrest Xia forres...@gmail.com +1 Did some testing on this RC1 with eclipse 3.5.2 java ee build, everything looks fine, thanks Delos! Forrest -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] Yoko 1.1 with osgi
The bad checksums seem to be because somehow maven 2.2.0 got installed on my system. I have no idea why, but it's known to produce bad checksums. I'll try to contact e.g. brian fox to see what we can do about them. I think usually what has happened in the past is to promote, then fix, but maybe they can be fixed before promotion. thanks david jencks On Apr 25, 2010, at 12:25 PM, Kevan Miller wrote: I'm seeing one blocker issue -- all of the checksums that I have downloaded do not match the corresponding checksums that I compute. For instance: $ md5sum yoko-1.1-source-release.tar.gz ; cat yoko-1.1-source-release.tar.gz.md5 md5sum yoko-1.1-source-release.tar.gz ; cat yoko-1.1-source-release.tar.gz.md5 f9283f77a4dfbfa483a085fb073bc3f7 yoko-1.1-source-release.tar.gz e849d7acbeafe1726252619e651f534c Until these are fixed, I'm -1 for the release. I'm ok with the vote proceeding, if these can be fixed in place (it doesn't look like the release artifacts need to be updated, just the checksums). There's one minor issue in the NOTICE file. The COPYRIGHT date has not been updated: Copyright 1999-2008 The Apache Software Foundation Our convention has been to keep the last year up to date, upon the release. This is not a requirement... --kevan On Apr 22, 2010, at 10:38 PM, David Jencks wrote: Please vote on yoko 1.1, yoko with osgi support. It works enough so an ORB and HandleDelegate can be bound in jndi. There are no non-classloading related code changes from previous yoko releases. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-013/ Tag: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.1/
[BUILD] trunk: Failed for Revision: 937907
Geronimo Revision: 937907 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100425/unit-test-reports Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:711) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-api -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-api:jar:1.4.1-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.ops4j.pax.logging -DartifactId=pax-logging-service -Dversion=1.4.1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT 2) org.ops4j.pax.logging:pax-logging-service:jar:1.4.1-SNAPSHOT -- 2 required artifacts are missing. for artifact: org.apache.geronimo.testsupport:testsupport-common:jar:3.0-SNAPSHOT from the specified remote repositories: ops4j.snapshots (http://repository.ops4j.org/mvn-snapshots/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus
Re: osgi finder method to xbean?
Sounds good to me. Jarek On Fri, Apr 23, 2010 at 8:20 PM, David Jencks david_jen...@yahoo.com wrote: Jarek has written a bunch of useful looking osgi utility type stuff currently in geronimo-kernel. At least one of the classes, BundleAnnotationFinder, could be quite useful to other projects, so it might be a good idea to move it to xbean-finder. However, it uses many of the other classes. So how about moving all the non-geronimo-specific osgi utility classes to a new xbean-osgi that can be used by the osgi support in xbean-finder? thanks david jencks
[jira] Created: (GERONIMODEVTOOLS-643) Refactor GEP 3.0 code to decouple various server adapters
Refactor GEP 3.0 code to decouple various server adapters - Key: GERONIMODEVTOOLS-643 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-643 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 GEP 3.0 will contain server adapters of all versions, including v1.1,v2.0,v2.1,v2.2,v3.0. It makes current GEP code much complicated. IMO, we have following guideline of GEP structure design 1) org.apache.geronimo.st.core and org.apache.geronimo.st.ui has common functions used by various adapters. These two plug-ins shouln't depend on any version specific adapter plug-in, such as org.apache.geronimo.runtime.vXX,org.apache.geronimo.st.vXX.core and org.apache.geronimo.st.vXX.ui 2) org.apache.geronimo.j2ee.v11.jaxbmodel is dedicated to v11 adapter, while org.apache.geronimo.jee.v21.jaxbmodel is for v20,v21,v22 adapter. So far, no jaxb model updated for v30, so v30 adapter still depends on org.apache.geronimo.jee.v21.jaxbmodel 3 )Since v20,v21 and v22 adapters all depends on v21 jaxb model , they shared operations on the model. Currently, we put all their shared operations in org.apache.geronimo.st.v21.core and org.apache.geronimo.st.v21.ui. Both plug-ins of v20 and v21 adapters depend on them. 4) For v11 adapter, it's the only adapter for JEE 4 and it depends on v11 jaxb model. Except common functions in org.apache.geronimo.st.core, it doesn't have much in common with other adapter. 5) For v30 adapter, it's the only adapter for JavaEE 6. Currently, since it still uses v21 jaxb model, it needs operations on the model. As a result, V30 plug-in still depends on org.apache.geronimo.st.v21.core and org.apache.geronimo.st.v21.ui. In future, once updated jaxb model for v30 is added, we will remove v21.core and v21.ui from its dependency list. Unfortunately, current GEP code doesn't strictly obey the guideline above. So I did some refactoring work for GEP 3.0 code. I won't commit the change until we get an agreement on this. I hope all of us are able to have the same undertstanding on GEP structure. It will avoid potential confusion in future. Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
