[BUILD] trunk: Failed for Revision: 937572
Geronimo Revision: 937572 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/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?
That sounds a great idea to me! Lin On Fri, Apr 23, 2010 at 8:20 PM, David Jencks 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 > >
osgi finder method to xbean?
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: (GERONIMO-5270) Enforce Java1.6 for Geronimo 3.0 build in maven and perhaps enforce the required maven version as well (2.2.1?).
Enforce Java1.6 for Geronimo 3.0 build in maven and perhaps enforce the required maven version as well (2.2.1?). - Key: GERONIMO-5270 URL: https://issues.apache.org/jira/browse/GERONIMO-5270 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0 Reporter: Joe Bohn Fix For: 3.0 I believe that Geronimo 3.0 must be built using java 1.6 and fails if that is not the case. However, it isn't a nice failure. We should configure maven to check the java version and fail if it isn't 1.6. We should also consider checking the maven version and enforcing a minimum maven version - I've heard that 2.2.1 is required. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 937472
Geronimo Revision: 937472 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/build-1500.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 45 minutes 10 seconds [INFO] Finished at: Fri Apr 23 15:48:58 EDT 2010 [INFO] Final Memory: 524M/1014M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/logs-1500-tomcat/ Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.449 sec <<< FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.446 sec <<< FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/logs-1500-jetty/ [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retri
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
+1 Looks good to me. I built the specs, checked rat, etc... included them (and the aries artifacts up for vote) in a Geronimo 3.0 server image and was able to deploy and run the Aries Blog & AriesTrader samples. Joe On 4/22/10 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)
[VOTE] Release OpenJPA-2.0.0 Plugins for Geronimo 2.2-2.2.1 servers
I've created a release candidate of a set of plugins that can be used to upgrade an existing Geronimo 2.2 or 2.2.1-SNAPSHOT server from OpenJPA 1.x to the new OpenJPA 2.0.0 release, so users can start experimenting with a JPA 2.0 certified codebase. You can install the plugins by using the console Plugin portlet and Updating the existing plugin repos to see the g.a.o/plugins/openjpa2 or you can try using the following mirror catalog site: http://people.apache.org/~dwoods/geronimo/openjpa2/ Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-018/ Source tag: https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/tags/2.2/ Source tar/zips: https://repository.apache.org/content/repositories/orgapachegeronimo-018/org/apache/geronimo/plugins/openjpa2/2.2/ For plugin installation instructions, see: https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/tags/2.2/README.txt Note: There are 2 plugins at version 2.2 to install (openjpa2 and persistence-deployer-jpa20.) You will need to restart your server before running or deploying apps that need JPA2 so the artifactAlias entries will take affect and replace already loaded OpenJPA 1.x and spec jars. The latest version of Daytrader 2.2-SNAPSHOT that can be used for testing can be installed as a plugin from the normal plugin repos. Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
[VOTE] Release OpenJPA-2.0.0 Plugins for Geronimo 2.1.3-2.1.5 servers
I've created a release candidate of a set of plugins that can be used to upgrade an existing Geronimo 2.1.3, 2.1.4, 2.1.5 or 2.1.6-SNAPSHOT server from OpenJPA 1.x to the new OpenJPA 2.0.0 release, so users can start experimenting with a JPA 2.0 certified codebase. You can install the plugins by using the console Plugin portlet and Updating the existing plugin repos to see the g.a.o/plugins/openjpa2 or you can try using the following mirror catalog site: http://people.apache.org/~dwoods/geronimo/openjpa2/ Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-017/ Source tag: https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/tags/2.1.3/ Source tar/zips: https://repository.apache.org/content/repositories/orgapachegeronimo-017/org/apache/geronimo/plugins/openjpa2/2.1.3/ For plugin installation instructions, see: https://svn.apache.org/repos/asf/geronimo/plugins/openjpa2/tags/README.txt Note: There are 2 plugins at version 2.1.3 to install (openjpa2 and persistence-deployer-jpa20.) You will need to restart your server before running or deploying apps that need JPA2 so the artifactAlias entries will take affect and replace already loaded OpenJPA 1.x and spec jars. The latest version of Daytrader 2.1.3 that can be used for testing can be installed as a plugin from: http://people.apache.org/~dwoods/daytrader-2.1.3/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald
Re: [VOTE] Release Geronimo Java EE specs (attempt THREE)
Believe these are okay after second look. +1 -Donald On 4/22/10 3:43 PM, Donald Woods wrote: > Here are 3 scripts to help checkout, rat:check and build the > tags in the vote. > > 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/ > > > > -Donald > > > On 4/22/10 1:03 PM, Rick McGuire wrote: >> On 4/22/2010 12:58 PM, Donald Woods wrote: >>> 1) Rick, I think the staging repo included below is for the RC2 vote. >>> Shouldn't it be - >>> https://repository.apache.org/content/repositories/orgapachegeronimo-007/ >>> >>> 2) You hadn't dropped the previous 030 staging files in Nexus yet (from >>> 4/16), so I did that for you. >>> >> Thanks. I remembered at one point that I needed to so that, but forgot >> to go back and do the actual trop. >> >>> 3) The JPA spec below should be listed as geronimo-jpa_2.0_spec-1.1, >>> based on the tag and files in the 007 staging repo. >>> >> >> Unless I'm missing something, that's exactly how it IS listed. I >> corrected the error of the last cycle to make this 1.1 not 1.2. >> >> Rick >>> >>> -Donald >>> >>> >>> On 4/22/10 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) >>> >> >>
[jira] Commented: (GERONIMO-5253) Expose java:app/AppName and java:module/ModuleName in JNDI
[ https://issues.apache.org/jira/browse/GERONIMO-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860358#action_12860358 ] Jarek Gawor commented on GERONIMO-5253: --- Added tests to testsuite for injecting java:app/AppName and java:module/ModuleName. Committed in revision 937484. > Expose java:app/AppName and java:module/ModuleName in JNDI > -- > > Key: GERONIMO-5253 > URL: https://issues.apache.org/jira/browse/GERONIMO-5253 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, Web Profile >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0 > > > Expose java:app/AppName and java:module/ModuleName in JNDI. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] Release Geronimo Bundles components for the Geronimo 3.0-M1 release
To support the upcoming Geronimo milestone release, I would like to the newly created bundles components. This components are versions of external Geronimo dependencies that have been converted into OSGi jars. This is a single vote for all of the converted dependencies required for the Geronimo 3.0-M1 release. A note on the bundle version numbers. The numbering scheme uses the version number from the original component jar, with a Geronimo version number added using a "_n" suffix (all of these are the "_1" version). The Derby version, 10.5.3.0_1_1 is not a type. This is the wrappering based on the 10.5.3.0_1 version of Derby. The RAT and IANAL plugins have been run against of the projects. 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-016/ All source repos are relative to location https://svn.apache.org/repos/asf/geronimo/bundles/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 components are being voted on bundles-parent-1.0 (this is just the parent pom for all of the bundle components) aspectjrt-1.6.2_1 aspectjweaver-1.6.2_1 axis-1.4_1 backport-util-concurrent-2.2_1 castor-1.0.5_1 commons-digester-1.8_1 commons-discovery-0.4_1 derby-all-10.5.3.0_1_1 dwr-3.0.M1_1 httpcore-4.0.1_1 jaxb-impl-2.2_1 jstl-1.2_1 scannotation-1.0.2_1 sxc-jaxb-0.7.2_1 sxc-runtime-0.7.2_1 wadi-aop-2.1.2_1 wadi-core-2.1.2_1 wadi-group-2.1.2_1 wadi-tribes-2.1.2_1 woden-impl-dom-1.0M8_1 woodstox-3.2.9_1
Re: [VOTE] Yoko 1.1 with osgi
+1 Looks good. -Donald On 4/22/10 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/ > > Vote open for 72 hours > > thanks > david jencks
[jira] Commented: (GERONIMO-5113) Add naming builder support for processing DataSourceDefinition annotations.
[ https://issues.apache.org/jira/browse/GERONIMO-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860324#action_12860324 ] Jarek Gawor commented on GERONIMO-5113: --- Added a testsuite test case for @DataSourceDefinition (revision 937441). > Add naming builder support for processing DataSourceDefinition annotations. > > > Key: GERONIMO-5113 > URL: https://issues.apache.org/jira/browse/GERONIMO-5113 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: connector, javaee6 >Affects Versions: 3.0 >Reporter: Rick McGuire >Assignee: Jarek Gawor > Fix For: 3.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5269) ContainerBase.addChild: start: LifecycleException: java.io.IOException: Context did not start for an unknown reason
[ https://issues.apache.org/jira/browse/GERONIMO-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-5269. -- Resolution: Duplicate oops. > ContainerBase.addChild: start: LifecycleException: java.io.IOException: > Context did not start for an unknown reason > > > Key: GERONIMO-5269 > URL: https://issues.apache.org/jira/browse/GERONIMO-5269 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 2.1.5, 2.2, 3.0 >Reporter: Kevan Miller > > Failures of the following sort provide almost no information to users. The > underlying cause is hard to diagnose. We need to do something to provide more > information to users for this specific scenario. > ./bin/deploy.sh -v --user system --password manager deploy jms-webapp.war > Using GERONIMO_HOME: /opt/geronimo-tomcat6-minimal-2.2 > Using GERONIMO_TMPDIR: var/temp > Using JRE_HOME: > 22:49:03,936 INFO [AbstractGBeanReference] GBean references are not using > proxies > 22:49:04,212 INFO [MultiParentClassLoader] ClassLoading behaviour has > changed. The Original Classloading mode is in effect. If you are > experiencing a problem > you can change the behaviour by specifying > -DXorg.apache.geronimo.kernel.config.MPCLSearchOption= property. Specify > ="safe" to revert to the original behaviour. This is a temporary change > until we decide whether or not to make it > permanent for the 2.0 release > 2010-04-22 22:49:13,247 ERROR [DeployTool] Error: > org.apache.geronimo.common.DeploymentException: Operation failed: start of > org.foo/jms-webapp/1.0-SNAPSHOT/war failed > org.apache.geronimo.kernel.config.LifecycleException: start of > org.foo/jms-webapp/1.0-SNAPSHOT/war failed > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) > at > org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) > 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) > at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) > at > javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) > at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) > at sun.rmi.transport.Tran
[jira] Created: (GERONIMO-5269) ContainerBase.addChild: start: LifecycleException: java.io.IOException: Context did not start for an unknown reason
ContainerBase.addChild: start: LifecycleException: java.io.IOException: Context did not start for an unknown reason Key: GERONIMO-5269 URL: https://issues.apache.org/jira/browse/GERONIMO-5269 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 2.2, 2.1.5, 3.0 Reporter: Kevan Miller Failures of the following sort provide almost no information to users. The underlying cause is hard to diagnose. We need to do something to provide more information to users for this specific scenario. ./bin/deploy.sh -v --user system --password manager deploy jms-webapp.war Using GERONIMO_HOME: /opt/geronimo-tomcat6-minimal-2.2 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: 22:49:03,936 INFO [AbstractGBeanReference] GBean references are not using proxies 22:49:04,212 INFO [MultiParentClassLoader] ClassLoading behaviour has changed. The Original Classloading mode is in effect. If you are experiencing a problem you can change the behaviour by specifying -DXorg.apache.geronimo.kernel.config.MPCLSearchOption= property. Specify ="safe" to revert to the original behaviour. This is a temporary change until we decide whether or not to make it permanent for the 2.0 release 2010-04-22 22:49:13,247 ERROR [DeployTool] Error: org.apache.geronimo.common.DeploymentException: Operation failed: start of org.foo/jms-webapp/1.0-SNAPSHOT/war failed org.apache.geronimo.kernel.config.LifecycleException: start of org.foo/jms-webapp/1.0-SNAPSHOT/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$Conne
Re: [VOTE] Yoko 1.1 with osgi
+1 ran RAT and IANAL and built from source. RAT is giving a some failures, but the failures are either missing copyrights in NOTICES.vm and LEGAL.vm files or in the source files that are directly generated from the idl files. I don't think either problem is serious enough to require a redo, particularly since these same issues were in the 1.0 release as well. Rick On 4/22/2010 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/ Vote open for 72 hours thanks david jencks
File permissions of /www/geronimo.apache.org/
Jason, I assume you're the owner of some script that is extracting and copying geronimo/site/trunk/docs/ from svn over to /www/geronimo.apache.org/ every hour+5 mins? If so, can you fix it, so the files have g+w set? Other choice, would be to have infra setup svnpubsub for those files in svn over to our www dir, so no one has to own such scripts. Thanks, Donald
[jira] Created: (GERONIMO-5268) Context did not start for an unknown reason -- does not help identify the true cause of a deployment failure
Context did not start for an unknown reason -- does not help identify the true cause of a deployment failure Key: GERONIMO-5268 URL: https://issues.apache.org/jira/browse/GERONIMO-5268 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.2, 2.1.5, 3.0 Reporter: Kevan Miller Errors like the following are difficult to debug/diagnose. We should do something to make it easier for users to diagnose the actual issue. $ ./bin/deploy.sh -v --user system --password manager deploy jms-webapp.war Using GERONIMO_HOME: /opt/geronimo-tomcat6-minimal-2.2 Using GERONIMO_TMPDIR: var/temp Using JRE_HOME: 22:49:03,936 INFO [AbstractGBeanReference] GBean references are not using proxies 22:49:04,212 INFO [MultiParentClassLoader] ClassLoading behaviour has changed. The Original Classloading mode is in effect. If you are experiencing a problem you can change the behaviour by specifying -DXorg.apache.geronimo.kernel.config.MPCLSearchOption= property. Specify ="safe" to revert to the original behaviour. This is a temporary change until we decide whether or not to make it permanent for the 2.0 release 2010-04-22 22:49:13,247 ERROR [DeployTool] Error: org.apache.geronimo.common.DeploymentException: Operation failed: start of org.apache.activemq.book/jms-webapp/1.0-SNAPSHOT/war failed org.apache.geronimo.kernel.config.LifecycleException: start of org.apache.activemq.book/jms-webapp/1.0-SNAPSHOT/war failed at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:562) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:851) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.Th
[BUILD] trunk: Failed for Revision: 937280
Geronimo Revision: 937280 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/build-0900.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 23 minutes 43 seconds [INFO] Finished at: Fri Apr 23 10:11:04 EDT 2010 [INFO] Final Memory: 607M/740M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/logs-0900-tomcat/ Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure; ignoring: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused] [org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to: service:jmx:rmi://localhost
Re: Items we need to complete for the M1 release
On 4/23/2010 10:35 AM, Joe Bohn wrote: One more SNAPSHOT that may be missing from the #2 list below: geronimo-concurrent_1.0_spec - what are the plans for this? We're using a snapshot in trunk but I don't see it included in the current set of specs up for vote. The concurrent stuff is a bit of a problem. I suspect we need to just disable that, since that early experimental version has serious OSGi split-package issues. I don't believe the concurrent plugin will even build at the moment. Rick Joe On 4/22/10 2:17 PM, Rick McGuire wrote: Ok, I've put together a set of items that need to be completed for the M1 release. Here are the items I'm aware of: Ok, the following things need to be done: 1) Get the specs released (up for vote now) 2) Release the various Geronimo subprojects the server is dependent upon - Geronimo bundles (I'm currently moving those out of the server build and getting the license issues sorted out) - XBeans blueprint - yoko - The components components (transaction manager, connector, jaspi) - The xmlbeans schema components - Our version of tomcat in the external release 3) Sort out how to deal with our current snapshot dependencies. This includes (but not limited to): - openejb - activemq - aries (currently up for release vote) - pax-logging - some servicemix bundles - myfaces - felix bundlerepository - felix karaf - juddi - tranql-connector - openwebbeans (recently added to the build) Rick
Re: Items we need to complete for the M1 release
One more SNAPSHOT that may be missing from the #2 list below: geronimo-concurrent_1.0_spec - what are the plans for this? We're using a snapshot in trunk but I don't see it included in the current set of specs up for vote. Joe On 4/22/10 2:17 PM, Rick McGuire wrote: Ok, I've put together a set of items that need to be completed for the M1 release. Here are the items I'm aware of: Ok, the following things need to be done: 1) Get the specs released (up for vote now) 2) Release the various Geronimo subprojects the server is dependent upon - Geronimo bundles (I'm currently moving those out of the server build and getting the license issues sorted out) - XBeans blueprint - yoko - The components components (transaction manager, connector, jaspi) - The xmlbeans schema components - Our version of tomcat in the external release 3) Sort out how to deal with our current snapshot dependencies. This includes (but not limited to): - openejb - activemq - aries (currently up for release vote) - pax-logging - some servicemix bundles - myfaces - felix bundlerepository - felix karaf - juddi - tranql-connector - openwebbeans (recently added to the build) Rick
[jira] Updated: (GERONIMO-5259) Annoying "access denied" security exceptions for oenwebbeans while java2 security is enabled.
[ https://issues.apache.org/jira/browse/GERONIMO-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-5259: --- Affects Version/s: 3.0 (was: 2.2) Patch Info: [Patch Available] > Annoying "access denied" security exceptions for oenwebbeans while java2 > security is enabled. > - > > Key: GERONIMO-5259 > URL: https://issues.apache.org/jira/browse/GERONIMO-5259 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 3.0 >Reporter: YING WANG >Assignee: Donald Woods >Priority: Minor > Fix For: 3.0 > > Attachments: 5259.patch, AnnotationLiteral.java > > > Hello neighbors, I am from the openwebbean project. while I am fixing owb-312 > (https://issues.apache.org/jira/browse/OWB-312), I found some of > AccessControlExceptions are fired fom javax.enterprise.util.AnnotationLiteral > in jcdi api. > Fixing the issue in OWB will be nasty since it is referenced all over the owb > code. > Could we add doPrivileged block around Class.setAccess() and > getDeclaredMethods calls in this class? > Thanks in advnace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5259) Annoying "access denied" security exceptions for oenwebbeans while java2 security is enabled.
[ https://issues.apache.org/jira/browse/GERONIMO-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-5259. Fix Version/s: 3.0 Resolution: Fixed Committed as r937297. Published updated 1.1-SNAPSHOT artifact (geronimo-jcdi_1.0_spec-1.1-20100423.134833-1.jar) to snapshot repo. > Annoying "access denied" security exceptions for oenwebbeans while java2 > security is enabled. > - > > Key: GERONIMO-5259 > URL: https://issues.apache.org/jira/browse/GERONIMO-5259 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 2.2 >Reporter: YING WANG >Assignee: Donald Woods >Priority: Minor > Fix For: 3.0 > > Attachments: 5259.patch, AnnotationLiteral.java > > > Hello neighbors, I am from the openwebbean project. while I am fixing owb-312 > (https://issues.apache.org/jira/browse/OWB-312), I found some of > AccessControlExceptions are fired fom javax.enterprise.util.AnnotationLiteral > in jcdi api. > Fixing the issue in OWB will be nasty since it is referenced all over the owb > code. > Could we add doPrivileged block around Class.setAccess() and > getDeclaredMethods calls in this class? > Thanks in advnace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5259) Annoying "access denied" security exceptions for oenwebbeans while java2 security is enabled.
[ https://issues.apache.org/jira/browse/GERONIMO-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods reassigned GERONIMO-5259: -- Assignee: Donald Woods > Annoying "access denied" security exceptions for oenwebbeans while java2 > security is enabled. > - > > Key: GERONIMO-5259 > URL: https://issues.apache.org/jira/browse/GERONIMO-5259 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Affects Versions: 2.2 >Reporter: YING WANG >Assignee: Donald Woods >Priority: Minor > Attachments: 5259.patch, AnnotationLiteral.java > > > Hello neighbors, I am from the openwebbean project. while I am fixing owb-312 > (https://issues.apache.org/jira/browse/OWB-312), I found some of > AccessControlExceptions are fired fom javax.enterprise.util.AnnotationLiteral > in jcdi api. > Fixing the issue in OWB will be nasty since it is referenced all over the owb > code. > Could we add doPrivileged block around Class.setAccess() and > getDeclaredMethods calls in this class? > Thanks in advnace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Items we need to complete for the M1 release
On 4/22/10 9:17 PM, chi runhua wrote: Any documents that we plan to announce together with M1 release, for example, how to build the Tomcat assembly, how to deploy Aries Blog sample application, a brief introduction of how Geronimo is integrated with OSGi Framework or any other topics? if so, we might need to create a new wiki space for G3.0. Comments? Yes, I think we need a new wiki page for 3.0. I was planning to put some doc out there on how to install & run the Aries Blog and AriesTrader samples. Joe Jeff On Fri, Apr 23, 2010 at 8:52 AM, Ivan mailto:xhh...@gmail.com>> wrote: For Tomcat, I would first try to pull the latest codes today, then we could begin for the release 2010/4/23 David Jencks mailto:david_jen...@yahoo.com>> On Apr 22, 2010, at 11:17 AM, Rick McGuire wrote: > Ok, I've put together a set of items that need to be completed for the M1 release. Here are the items I'm aware of: > > Ok, the following things need to be done: > > 1) Get the specs released (up for vote now) > 2) Release the various Geronimo subprojects the server is dependent upon >- Geronimo bundles (I'm currently moving those out of the server build and getting the license issues sorted out) >- XBeans blueprint >- yoko I'll start a vote today or tomorrow >- The components components (transaction manager, connector, jaspi) I want to review these for whether package changes to be more osgi friendly would work easily. >- The xmlbeans schema components AFAIK these should be ok to release anytime, Ivan might know more. >- Our version of tomcat in the external release > 3) Sort out how to deal with our current snapshot dependencies. This includes (but not limited to): >- openejb >- activemq >- aries (currently up for release vote) >- pax-logging >- some servicemix bundles >- myfaces They released 2.0.0 today maybe it will work for us. >- felix bundlerepository >- felix karaf >- juddi I'll try to get our build to work with the last released version. >- tranql-connector There are a couple patches here, then I'll release. >- openwebbeans (recently added to the build) thanks david jencks > > Rick -- Ivan
[BUILD] trunk: Failed for Revision: 937168
Geronimo Revision: 937168 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 43 minutes 46 seconds [INFO] Finished at: Fri Apr 23 03:49:35 EDT 2010 [INFO] Final Memory: 545M/1012M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/logs-0300-tomcat/ Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.559 sec <<< FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.644 sec <<< FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/logs-0300-jetty/ Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.446 sec <<< FAILURE! -- Running TestSuite Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.448 sec <<< FAILURE! Samples: trunk = Log: http://people.apache.org/builds/geronimo/server/binaries/trunk/20100423/samples-0300.log Build status: FAILED
Re: [VOTE] Geronimo Eclipse Plugin 2.1.5 RC1
Besides, we also get +1 from Ashish and Forrest, thanks! 2010/4/23 Delos > 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 > > +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: Items we need to complete for the M1 release
On Apr 22, 2010, at 11:17 AM, Rick McGuire wrote: > Ok, I've put together a set of items that need to be completed for the M1 > release. Here are the items I'm aware of: > > Ok, the following things need to be done: > > 1) Get the specs released (up for vote now) > 2) Release the various Geronimo subprojects the server is dependent upon >- Geronimo bundles (I'm currently moving those out of the server build and > getting the license issues sorted out) >- XBeans blueprint -- depends on aries blueprint >- yoko -- up for vote >- The components components (transaction manager, connector, jaspi) >- The xmlbeans schema components >- Our version of tomcat in the external release > 3) Sort out how to deal with our current snapshot dependencies. This > includes (but not limited to): >- openejb >- activemq >- aries (currently up for release vote) >- pax-logging >- some servicemix bundles >- myfaces -- done, moved to latest released 2.0.0. >- felix bundlerepository >- felix karaf >- juddi -- done. This builds but a server with it doesn't start. I included it into the build anyway. > - tranql-connector >- openwebbeans (recently added to the build) > > Rick david jencks
[jira] Commented: (GERONIMO-5005) uddi osgi integration
[ https://issues.apache.org/jira/browse/GERONIMO-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860155#action_12860155 ] David Jencks commented on GERONIMO-5005: rev 937169 uses latest released juddi. It builds but the test server does not start. Current problem is that juddi appears to be trying to configure log4j. We'll have to discuss this with the juddi project. > uddi osgi integration > - > > Key: GERONIMO-5005 > URL: https://issues.apache.org/jira/browse/GERONIMO-5005 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: javaee6, osgi >Affects Versions: 3.0 >Reporter: David Jencks > Fix For: 3.0 > > > Upgrade uddi support to osgi and also up to date juddi. Juddi needs to apply > JUDDI-299 which among other things bundleizes juddi. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
