[jira] Resolved: (GERONIMO-4492) Unable to convert resource archives into plugin from console
[ https://issues.apache.org/jira/browse/GERONIMO-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-4492. -- Assignee: Chi Runhua Fix Version/s: 2.2 (was: 2.2.1) Resolution: Fixed Already documented in G2.2. See the info at https://cwiki.apache.org/confluence/display/GMOxDOC22/New+features+and+enhancements Jeff > Unable to convert resource archives into plugin from console > - > > Key: GERONIMO-4492 > URL: https://issues.apache.org/jira/browse/GERONIMO-4492 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Plugins >Affects Versions: 2.2 > Environment: WinXP Professional+Sun Java 1.6+ > geronimo-tomcat6-javaee5-2.2-SNAPSHOT 1229 build >Reporter: Chi Runhua >Assignee: Chi Runhua > Fix For: 2.2 > > > Create a new derby database and then setup a datasource pool for it, > jdbc/userdbs; > Log into the admin console and go to Plugins; > Select Create Geronimo Plugin and click on drop-down list; > console/dbpool/jdbc_userdbs/1.0/rar is not in the list. > Notes: .ear, .jar and .war don't have the same problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864638#action_12864638 ] Tang Yin Qi edited comment on GERONIMO-5273 at 5/6/10 12:48 AM: OK. It's my new patch from the root directory. was (Author: tang yin qi): OK. It's my new patch form the root directory. > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 3.0 > > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
OSGi version for Geronimo packages
Hi, Before the milestone release we might have to figure out what osgi version (if any) the Geronimo packages should be exported at. I can think of a few possibilities: 1) No version exported for milestone releases. In the final release everything would be exported with "3.0.0" version. 2) Use version "3.0.0" for milestones and final release. Milestones are milestones and should not be used once the final is out. 3) Add some qualifier to the osgi version for milestone and final releases. We just need to be careful to pick the right qualifiers so that osgi resolves to the latest version. For example for milestones we could assign "3.0.0.M1" or "3.0.0.M2" but for the final we would have to assign "3.0.0.final" or some other qualifier that is greater then 'Mx' using String.compareTo() rules. Thoughts or any other possibilities? I like #3 (or some version of it) but I'm also ok with #2. Jarek
[jira] Closed: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5273. - Fix Version/s: 3.0 Resolution: Fixed Committed revision 941569. Thanks Tang Yin Qi for providing this patch. > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 3.0 > > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: (was: GERONIMO-5273.patch) > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864638#action_12864638 ] Tang Yin Qi commented on GERONIMO-5273: --- OK. It's my new patch form the root directory. > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: GERONIMO-5273.patch > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch, GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864632#action_12864632 ] Forrest Xia commented on GERONIMO-5273: --- pls make the patch from the root directory of samples trunk. > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4637) Need documents on how to replace default file realm in Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua resolved GERONIMO-4637. -- Assignee: Chi Runhua Resolution: Fixed Doc is already updated for G2.2. > Need documents on how to replace default file realm in Geronimo > --- > > Key: GERONIMO-4637 > URL: https://issues.apache.org/jira/browse/GERONIMO-4637 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 2.2 >Reporter: Chi Runhua >Assignee: Chi Runhua >Priority: Minor > Fix For: 2.2.1 > > > The default security realm is of properties files in Geronimo. While Geronimo > supports another 2 types of security realm such as SQL and LDAP. It would be > nice if we have tutorials on how to replace the default one with SQL or LDAP > realms. > Jeff C -- 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: 941556
Geronimo Revision: 941556 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 46 minutes 36 seconds
[INFO] Finished at: Wed May 05 21:51:16 EDT 2010
[INFO] Final Memory: 545M/993M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/logs-2100-tomcat/
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/plugins/maven-failsafe-plugin/2.5/maven-failsafe-plugin-2.5.jar
46K downloaded (maven-failsafe-plugin-2.5.jar)
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-selenium:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.testsupport:testsupport:3.0-SNAPSHOT:
checking for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from codehaus.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from jetty.oss.sonatype.org
[INFO] snapshot
org.apache.geronimo.testsupport:testsupport-common:3.0-SNAPSHOT: checking for
updates from openqa-snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from codehaus.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from jetty.oss.sonatype.org
[INFO] snapshot org.apache.geronimo.framework:modules:3.0-SNAPSHOT: checking
for updates from openqa-snapshots
[INFO] [enforcer:enforce {execution: default}]
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-booter/2.5/surefire-booter-2.5.pom
1K downloaded (surefire-booter-2.5.pom)
Downloading:
file:///home/geronimo/.m2/jtidy.repository/org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.pom
[INFO] Unable to find resource 'org.apache.maven.surefire:surefire-api:pom:2.5'
in repository local (file:///home/geronimo/.m2/jtidy.repository)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.pom
2K downloaded (surefire-api-2.5.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-utils/1.5.9/plexus-utils-1.5.9.pom
5K downloaded (plexus-utils-1.5.9.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/maven-toolchain/2.0.9/maven-toolchain-2.0.9.pom
3K downloaded (maven-toolchain-2.0.9.pom)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-booter/2.5/surefire-booter-2.5.jar
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/codehaus/plexus/plexus-utils/1.5.9/plexus-utils-1.5.9.jar
262K downloaded (plexus-utils-1.5.9.jar)
313K downloaded (surefire-booter-2.5.jar)
Downloading:
file:///home/geronimo/.m2/jtidy.repository/org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
[INFO] Unable to find resource 'org.apache.maven.surefire:surefire-api:jar:2.5'
in repository local (file:///home/geronimo/.m2/jtidy.repository)
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/maven/surefire/surefire-api/2.5/surefire-api-2.5.jar
557K downloaded (surefire-api-2.5.jar)
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] No tests to run.
[INFO] [ianal:verify-legal-files {
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
Agree, We can just add a comment in its pom, which records the revision our external tomcat based on. -Rex 2010/5/6 Ivan > I think that our four version numbers could help us, while Tomcat always > has three version number. In next iteration, we call our version 7.0.0.1, > which means more changes are merged from Tomcat 7 dev tree .. > > 2010/5/5 Vamsavardhana Reddy > > >> >> On Wed, May 5, 2010 at 7:45 PM, Kevan Miller wrote: >> >>> >>> On May 4, 2010, at 1:56 PM, Joe Bohn wrote: >>> >>> > >>> > +1 (assuming the potential license issue mentioned below is not an >>> issue) >>> > >>> > I was able to build and run the new tomcat image. >>> > >>> > The license issue pointed out last time is now resolved but there is >>> one other potential issue. I noticed a number of files under jasper-el that >>> are generated using JJTree & JavaCC and so have the following header but no >>> Apache license header. For example: >>> > >>> > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ >>> > >>> > Some other generated files include both a generated header and which is >>> immediately followed by the Apache license header. This seems a little >>> better to me. However, I see that we have released these without the Apache >>> header in earlier versions (and Tomcat as well) - so I presume there must be >>> some valid justification for not including an Apache License header in these >>> files. Just pointing it out now in case it really needs some attention and >>> has just escaped being noticed until now. Comments? >>> >>> I've certainly noticed them in the past... Machine generated files do not >>> require license headers. So, IMO, these files are fine. >>> >>> I do have a question about the version #. IIUC, we are releasing 7.0.0 >>> prior to the TC community. There may be fixes applied to the Tomcat dev tree >>> prior to their 7.0 release. So, this release may not exactly match the >>> functionality of the tomcat release. Is everyone evaluating that in their >>> decision? >>> >>> --kevan >> >> >> I think there are two many zeros in the version number too. How about we >> use a version number similar to "6.0.18-G678601" like we have in G 2.x >> builds? >> >> -- >> Vamsi >> > > > > -- > Ivan > -- Lei Wang (Rex) rwonly AT apache.org
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
IIRC I came up with the 4 digits and I was thinking exactly this, we can release many ports of a given tomcat release this way. Having the same number of digits as tomcat won't work. If they used 4 we'd be in trouble :-) thanks david jencks On May 5, 2010, at 5:43 PM, Ivan wrote: > I think that our four version numbers could help us, while Tomcat always has > three version number. In next iteration, we call our version 7.0.0.1, which > means more changes are merged from Tomcat 7 dev tree .. > > 2010/5/5 Vamsavardhana Reddy > > > On Wed, May 5, 2010 at 7:45 PM, Kevan Miller wrote: > > On May 4, 2010, at 1:56 PM, Joe Bohn wrote: > > > > > +1 (assuming the potential license issue mentioned below is not an issue) > > > > I was able to build and run the new tomcat image. > > > > The license issue pointed out last time is now resolved but there is one > > other potential issue. I noticed a number of files under jasper-el that > > are generated using JJTree & JavaCC and so have the following header but no > > Apache license header. For example: > > > > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ > > > > Some other generated files include both a generated header and which is > > immediately followed by the Apache license header. This seems a little > > better to me. However, I see that we have released these without the > > Apache header in earlier versions (and Tomcat as well) - so I presume there > > must be some valid justification for not including an Apache License header > > in these files. Just pointing it out now in case it really needs some > > attention and has just escaped being noticed until now. Comments? > > I've certainly noticed them in the past... Machine generated files do not > require license headers. So, IMO, these files are fine. > > I do have a question about the version #. IIUC, we are releasing 7.0.0 prior > to the TC community. There may be fixes applied to the Tomcat dev tree prior > to their 7.0 release. So, this release may not exactly match the > functionality of the tomcat release. Is everyone evaluating that in their > decision? > > --kevan > > I think there are two many zeros in the version number too. How about we use > a version number similar to "6.0.18-G678601" like we have in G 2.x builds? > > -- > Vamsi > > > > -- > Ivan
Re: error starting the karaf shell when starting the server or deploy script
Yeah, you can ignore for now. Waiting for sshd 0.4 to be released. The published 0.4-SNAPSHOT has some other issues. Jarek On Wed, May 5, 2010 at 5:36 PM, Joe Bohn wrote: > After recently updating and building Geronimo to rev. 941434 I'm seeing an > error starting the tomcat javaee6 assembly or the deploy script: > > Using JRE_HOME: > /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home > Artifact org/apache/sshd/sshd-core/0.3.0/sshd-core-0.3.0.jar not found > ERROR: Error starting > mvn:org.apache.felix.karaf.shell/org.apache.felix.karaf.shell.ssh/1.5.0-SNAPSHOT > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.felix.karaf.shell.ssh [47]: package; > (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0 > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.felix.karaf.shell.ssh [47]: package; > (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0))) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3299) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1657) > at > org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) > at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) > at java.lang.Thread.run(Thread.java:637) > > Aside from the error things seem to be mostly working. > > Joe >
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
I think that our four version numbers could help us, while Tomcat always has three version number. In next iteration, we call our version 7.0.0.1, which means more changes are merged from Tomcat 7 dev tree .. 2010/5/5 Vamsavardhana Reddy > > > On Wed, May 5, 2010 at 7:45 PM, Kevan Miller wrote: > >> >> On May 4, 2010, at 1:56 PM, Joe Bohn wrote: >> >> > >> > +1 (assuming the potential license issue mentioned below is not an >> issue) >> > >> > I was able to build and run the new tomcat image. >> > >> > The license issue pointed out last time is now resolved but there is one >> other potential issue. I noticed a number of files under jasper-el that are >> generated using JJTree & JavaCC and so have the following header but no >> Apache license header. For example: >> > >> > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ >> > >> > Some other generated files include both a generated header and which is >> immediately followed by the Apache license header. This seems a little >> better to me. However, I see that we have released these without the Apache >> header in earlier versions (and Tomcat as well) - so I presume there must be >> some valid justification for not including an Apache License header in these >> files. Just pointing it out now in case it really needs some attention and >> has just escaped being noticed until now. Comments? >> >> I've certainly noticed them in the past... Machine generated files do not >> require license headers. So, IMO, these files are fine. >> >> I do have a question about the version #. IIUC, we are releasing 7.0.0 >> prior to the TC community. There may be fixes applied to the Tomcat dev tree >> prior to their 7.0 release. So, this release may not exactly match the >> functionality of the tomcat release. Is everyone evaluating that in their >> decision? >> >> --kevan > > > I think there are two many zeros in the version number too. How about we > use a version number similar to "6.0.18-G678601" like we have in G 2.x > builds? > > -- > Vamsi > -- Ivan
[BUILD] branches/2.2: Failed for Revision: 941542
Geronimo Revision: 941542 built with tests included
See the full build-2000.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-2000.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 19 source files to
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@1afe1afe
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@11c011c0
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@11c011c0
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-cxf/2.2.1-SNAPSHOT/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, CXF :: CXF
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@1afe1afe
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@11c011c0
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@11c011c0
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.systempropertyprofileactiva...@1afe1afe
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@11c011c0
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.operatingsystemprofileactiva...@11c011c0
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added depen
[VOTE] Geronimo jaspi component 1.1
Please vote for the geronimo-jaspi 1.1 component. The major changes to this release are: - packaged as an osgi bundle - fairly non-functional classloading in 1.0 replaced by Rick's ProviderLocator that actually works in osgi. - dependencies upgraded to use bundleized dependencies. I spent some time trying to get the manifest entries to look reasonable to me. Since this is the first osgi release I put the package-version at 1.0. The import version ranges are <_versionpolicy>[$(version;==;$(@)),$(version;+;$(@))) for everything except the self-imports which are [1.0,1.1). I suppose it would have been better to use this version range for the jaspic spec as well, but I didn't. There's always something. Maybe next time the maven-bundle-plugin will do this for us. Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-012/ tag is here: https://svn.apache.org/repos/asf/geronimo/components/jaspi/tags/geronimo-jaspi-1.1/ Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) thanks david jencks
Re: error starting the karaf shell when starting the server or deploy script
I've recently upgraded karaf to sshd 0.4.0-snaphot, so that may be the reason. On Wed, May 5, 2010 at 23:36, Joe Bohn wrote: > After recently updating and building Geronimo to rev. 941434 I'm seeing an > error starting the tomcat javaee6 assembly or the deploy script: > > Using JRE_HOME: > /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home > Artifact org/apache/sshd/sshd-core/0.3.0/sshd-core-0.3.0.jar not found > ERROR: Error starting > mvn:org.apache.felix.karaf.shell/org.apache.felix.karaf.shell.ssh/1.5.0-SNAPSHOT > (org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.felix.karaf.shell.ssh [47]: package; > (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0 > org.osgi.framework.BundleException: Unresolved constraint in bundle > org.apache.felix.karaf.shell.ssh [47]: package; > (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0))) >at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3299) >at org.apache.felix.framework.Felix.startBundle(Felix.java:1657) >at > org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) >at > org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) >at java.lang.Thread.run(Thread.java:637) > > Aside from the error things seem to be mostly working. > > Joe > -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
error starting the karaf shell when starting the server or deploy script
After recently updating and building Geronimo to rev. 941434 I'm seeing an error starting the tomcat javaee6 assembly or the deploy script: Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Artifact org/apache/sshd/sshd-core/0.3.0/sshd-core-0.3.0.jar not found ERROR: Error starting mvn:org.apache.felix.karaf.shell/org.apache.felix.karaf.shell.ssh/1.5.0-SNAPSHOT (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.karaf.shell.ssh [47]: package; (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.felix.karaf.shell.ssh [47]: package; (&(package=org.apache.sshd.common)(version>=0.4.0)(!(version>=1.0.0))) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3299) at org.apache.felix.framework.Felix.startBundle(Felix.java:1657) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1128) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:637) Aside from the error things seem to be mostly working. Joe
[BUILD] trunk: Failed for Revision: 941430
Geronimo Revision: 941430 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 63 minutes 41 seconds
[INFO] Finished at: Wed May 05 16:08:26 EDT 2010
[INFO] Final Memory: 543M/996M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/logs-1500-tomcat/
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.567 sec <<<
FAILURE!
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/enterprise-testsuite/appname-tests/appname-ear/target/failsafe-reports
---
T E S T S
---
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.567 sec <<<
FAILURE!
Results :
Failed tests:
testAppNameInjection(org.apache.geronimo.testsuite.appname.ServletTest)
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
[INFO] [geronimo:undeploy-module {execution: undeploy}]
[INFO] Using non-artifact based module id:
org.apache.geronimo.testsuite/appname-ear/3.0-SNAPSHOT/ear
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
Parsing URI=deployer:geronimo:jmx://localhost:1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
Parsing URI=deployer:geronimo:jmx://localhost:1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] : Using
protocol=jmx, host=localhost, port=1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] : Using
JMXServiceURL with host=localhost, port=1099, secure=false
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
throwing
javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException:
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]
at
org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.newRemoteDeploymentManager(BaseDeploymentFactory.java:193)
at
org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.getDeploymentManager(BaseDeploymentFactory.java:140)
at
javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManager.java:111)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.getDeploymentManager(ModuleMojoSupport.java:91)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.stopModule(ModuleMojoSupport.java:275)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.undeployModule(ModuleMojoSupport.java:309)
at
org.apache.geronimo.mavenplugins.geronimo.module.UndeployModuleMojo.doExecute(UndeployModuleMojo.java:37)
at
org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:99)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
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.j
[jira] Resolved: (GERONIMO-5286) Many irrelevant build properties end up in the manifest
[ https://issues.apache.org/jira/browse/GERONIMO-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-5286. Resolution: Fixed Committed revision 941475. > Many irrelevant build properties end up in the manifest > --- > > Key: GERONIMO-5286 > URL: https://issues.apache.org/jira/browse/GERONIMO-5286 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: Rick McGuire > Fix For: 3.0 > > > All the maven properties that start with an upper case letter are getting > added to every bundle manifest by the maven-bundle-plugin. > We need to determine if these properties are being used, if so if they are > needed, and if so change their case or preferably remove them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5213) Review Geronimo 3.0 commands need a thorough review
[ https://issues.apache.org/jira/browse/GERONIMO-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864459#action_12864459 ] Jarek Gawor commented on GERONIMO-5213: --- In revision 941434 I fixed the 'disconnect' shell command and updated the 'login' command to behave better in embedded mode. > Review Geronimo 3.0 commands need a thorough review > --- > > Key: GERONIMO-5213 > URL: https://issues.apache.org/jira/browse/GERONIMO-5213 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: commands >Affects Versions: 3.0 >Reporter: Kevan Miller >Assignee: Jarek Gawor > Fix For: 3.0 > > > The current set of Geronimo commands (geronimo, deploy, start, stop, > shutdown, admin, client) need to be reviewed for functionality. Mostly, they > are adopting gshell syntax/semantics. There needs to be a thorough review > that the new set of commands are providing all of the features/functions that > users are currently using. > I think having a single set of commands rather than the duplicate commands > (old and newer gshell-based commands) is good. There should be documentation > on how to migrate from the old environment to the new. For example, for > people using JAVA_OPTS / GERONIMO_OPTS how do they move to the new geronimo > command? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE] transaction manager component 3.0
Please vote for the geronimo transaction manager component consisting of the transaction manager and connector framework 3.0. The main changes in this release are: - connector 1.6 support - retry support in the transaction manager (not well tested yet). Due to the retry support the interfaces between these two jars have changed incompatibly, thus the jump to version 3. I've attempted to get reasonable osgi package version ranges in the manifests. Staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-011/ Tag is here: https://svn.apache.org/repos/asf/geronimo/components/txmanager/tags/geronimo-txmanager-parent-3.0/ Vote open 72 hours [ ] +1 release this [ ] 0 don't care [ ] -1 don't release this (please explain) thanks david jencks
[jira] Assigned: (GERONIMO-5286) Many irrelevant build properties end up in the manifest
[ https://issues.apache.org/jira/browse/GERONIMO-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire reassigned GERONIMO-5286: -- Assignee: Rick McGuire > Many irrelevant build properties end up in the manifest > --- > > Key: GERONIMO-5286 > URL: https://issues.apache.org/jira/browse/GERONIMO-5286 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0 >Reporter: David Jencks >Assignee: Rick McGuire > Fix For: 3.0 > > > All the maven properties that start with an upper case letter are getting > added to every bundle manifest by the maven-bundle-plugin. > We need to determine if these properties are being used, if so if they are > needed, and if so change their case or preferably remove them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 941395
Geronimo Revision: 941395 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-1400.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/ws/security/wss4j/1.5.8/wss4j-1.5.8.jar
316K downloaded
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/santuario/xmlsec/1.4.3/xmlsec-1.4.3.jar
437K downloaded
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/bouncycastle/bcprov-jdk15/1.43/bcprov-jdk15-1.43.jar
1594K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 19 source files to
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-cxf/2.2.1-SNAPSHOT/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, CXF :: CXF
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycl
Re: trunk build properties cleanup needed
On 5/5/2010 1:38 PM, David Jencks wrote: Someone needs to make all the maven properties start with a lowercase letter so they don't end up in the generated bundle manifest. I'm not at all sure that the properties like PlanServerHostname are still used, in which case they could be removed. If they are still used they could be made to start with a lowercase letter. See https://issues.apache.org/jira/browse/GERONIMO-5286 I was planning to look into this but getting supporting components ready to release is taking much longer than I planned for, so if anyone has some free time I'll take a look at doing this. Is this project confined to just the server build? Rick thanks david jencks
trunk build properties cleanup needed
Someone needs to make all the maven properties start with a lowercase letter so they don't end up in the generated bundle manifest. I'm not at all sure that the properties like PlanServerHostname are still used, in which case they could be removed. If they are still used they could be made to start with a lowercase letter. See https://issues.apache.org/jira/browse/GERONIMO-5286 I was planning to look into this but getting supporting components ready to release is taking much longer than I planned for, so if anyone has some free time thanks david jencks
[jira] Created: (GERONIMO-5286) Many irrelevant build properties end up in the manifest
Many irrelevant build properties end up in the manifest --- Key: GERONIMO-5286 URL: https://issues.apache.org/jira/browse/GERONIMO-5286 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0 Reporter: David Jencks Fix For: 3.0 All the maven properties that start with an upper case letter are getting added to every bundle manifest by the maven-bundle-plugin. We need to determine if these properties are being used, if so if they are needed, and if so change their case or preferably remove them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Where is source tree for geronimo-txmanager-parent 3.0-SNAPSHOT?
Joe has already found the parent for you :-) I'm working on cleaning up the poms here, mostly considering what package versions we might want on import and export, I hope to call a vote on this and the jaspi component later today. thanks david jencks On May 5, 2010, at 3:50 AM, Rick McGuire wrote: > On 5/5/2010 6:45 AM, Rick McGuire wrote: >> Doing some last minute dependency checking on the components. I see that >> the txmanager components have a parent pom of geronimo-txmanager-parent >> 3.0-SNAPSHOT, but I can't seem to find this version anywhere in the svn >> tree. The last version in tags is 2.1.4 and there is nothing in trunk for >> this. What am I missing here? > And looking at the version that got pulled from the snapshot repo, the > connector spec dependency in here really should be updated to the latest > released version. > > >> >> Rick >
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
On Wed, May 5, 2010 at 7:45 PM, Kevan Miller wrote: > > On May 4, 2010, at 1:56 PM, Joe Bohn wrote: > > > > > +1 (assuming the potential license issue mentioned below is not an issue) > > > > I was able to build and run the new tomcat image. > > > > The license issue pointed out last time is now resolved but there is one > other potential issue. I noticed a number of files under jasper-el that are > generated using JJTree & JavaCC and so have the following header but no > Apache license header. For example: > > > > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ > > > > Some other generated files include both a generated header and which is > immediately followed by the Apache license header. This seems a little > better to me. However, I see that we have released these without the Apache > header in earlier versions (and Tomcat as well) - so I presume there must be > some valid justification for not including an Apache License header in these > files. Just pointing it out now in case it really needs some attention and > has just escaped being noticed until now. Comments? > > I've certainly noticed them in the past... Machine generated files do not > require license headers. So, IMO, these files are fine. > > I do have a question about the version #. IIUC, we are releasing 7.0.0 > prior to the TC community. There may be fixes applied to the Tomcat dev tree > prior to their 7.0 release. So, this release may not exactly match the > functionality of the tomcat release. Is everyone evaluating that in their > decision? > > --kevan I think there are two many zeros in the version number too. How about we use a version number similar to "6.0.18-G678601" like we have in G 2.x builds? -- Vamsi
[jira] Resolved: (GERONIMO-5279) search-plugins, install-library deploy command fails with NoClassDefFoundError
[
https://issues.apache.org/jira/browse/GERONIMO-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-5279.
---
Assignee: Jarek Gawor
Fix Version/s: 3.0
Resolution: Fixed
Committed fixes for this problem in revision 941340. The gbean proxies did not
quite work in OSGi environment. Each proxy required access to some cglib
classes but not every bundle was importing the cglib packages. To fix this,
when a proxy is created, a proxy classloader is constructed that can delegates
the calls to the original classloader and a classloader that has access to the
cglib classes.
> search-plugins, install-library deploy command fails with NoClassDefFoundError
> --
>
> Key: GERONIMO-5279
> URL: https://issues.apache.org/jira/browse/GERONIMO-5279
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: commands, core
>Affects Versions: 3.0
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> Executing search-plugins, install-library deploy command fails with
> NoClassDefFoundError. Looks like the gbean proxying code needs to be fixed.
> Example:
> bin/deploy -u system -p manager install-library
> /home/gawor/.m2/repository/org/apache/felix/org.osgi.service.obr/1.0.2/org.osgi.service.obr-1.0.2.jar
> {code}
> java.lang.NoClassDefFoundError: [Lnet/sf/cglib/proxy/Callback;
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
> at java.lang.Class.getDeclaredMethods(Class.java:1791)
> at net.sf.cglib.core.ReflectUtils.addAllMethods(ReflectUtils.java:348)
> at
> net.sf.cglib.reflect.FastClassEmitter.(FastClassEmitter.java:66)
> at
> net.sf.cglib.reflect.FastClass$Generator.generateClass(FastClass.java:72)
> at
> net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25)
> at
> net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:216)
> at net.sf.cglib.reflect.FastClass$Generator.create(FastClass.java:64)
> at net.sf.cglib.reflect.FastClass.create(FastClass.java:46)
> at net.sf.cglib.reflect.FastClass.create(FastClass.java:39)
> at
> org.apache.geronimo.kernel.basic.BasicProxyManager$ManagedProxyFactory.(BasicProxyManager.java:204)
> at
> org.apache.geronimo.kernel.basic.BasicProxyManager.createProxyFactory(BasicProxyManager.java:78)
> at
> org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicProxyManager.java:104)
> at
> org.apache.geronimo.system.jmx.KernelDelegate.getGBean(KernelDelegate.java:109)
> at
> org.apache.geronimo.deployment.plugin.jmx.ExtendedDeploymentManager.getImplementation(ExtendedDeploymentManager.java:66)
> at
> org.apache.geronimo.deployment.plugin.jmx.ExtendedDeploymentManager.getPluginInstaller(ExtendedDeploymentManager.java:162)
> at
> org.apache.geronimo.deployment.plugin.jmx.ExtendedDeploymentManager.installLibrary(ExtendedDeploymentManager.java:220)
> at
> org.apache.geronimo.deployment.plugin.jmx.RemoteDeploymentManager.installLibrary(RemoteDeploymentManager.java:201)
> at
> org.apache.geronimo.deployment.cli.CommandInstallLibrary.execute(CommandInstallLibrary.java:52)
> at
> org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:173)
> at
> org.apache.geronimo.system.main.MainBridge.execute(MainBridge.java:64)
> at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:109)
> at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
> at
> org.apache.geronimo.cli.deployer.DeployerCLI.main(DeployerCLI.java:31)
> Caused by: java.lang.ClassNotFoundException: net.sf.cglib.proxy.Callback
> at
> org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:814)
> at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:61)
> at
> org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1733)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> {code}
--
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: 941274
Geronimo Revision: 941274 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 48 minutes 34 seconds
[INFO] Finished at: Wed May 05 09:53:11 EDT 2010
[INFO] Final Memory: 506M/1010M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/logs-0900-tomcat/
Running TestSuite
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.348 sec <<<
FAILURE!
[INFO] [0] org.apache.geronimo.testsuite/test-myfaces/3.0-SNAPSHOT/war
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING] org.apache.geronimo.testsuite:test-myfaces:war:3.0-SNAPSHOT
[INFO] [geronimo:stop-server {execution: stop-geronimo}]
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@1897b6f}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connected
[INFO] Stopping Geronimo server...
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-myfaces/target/test-myfaces-3.0-SNAPSHOT.war
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/test-myfaces/3.0-SNAPSHOT/test-myfaces-3.0-SNAPSHOT.war
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-myfaces/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: Web Testsuite :: Test Tomcat
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/test/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 1 source file to
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[test-tomcat] in
[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-tomcat-3.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp
webResources[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/main/webapp]
to[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-tomcat-3.0-SNAPSHOT]
[INFO] Copying webapp
webResources[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/classes]
to[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-tomcat-3.0-SNAPSHOT]
[INFO] Copying webapp
resources[/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/src/main/webapp]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-tomcat-3.0-SNAPSHOT/WEB-INF/lib/test-tomcat-3.0-SNAPSHOT.jar
[INFO] Webapp assembled in[52 msecs]
[INFO] Building war:
/home/geronimo/geronimo/trunk/testsuite/web-testsuite/test-tomcat/target/test-
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
On May 4, 2010, at 1:56 PM, Joe Bohn wrote: > > +1 (assuming the potential license issue mentioned below is not an issue) > > I was able to build and run the new tomcat image. > > The license issue pointed out last time is now resolved but there is one > other potential issue. I noticed a number of files under jasper-el that are > generated using JJTree & JavaCC and so have the following header but no > Apache license header. For example: > > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ > > Some other generated files include both a generated header and which is > immediately followed by the Apache license header. This seems a little > better to me. However, I see that we have released these without the Apache > header in earlier versions (and Tomcat as well) - so I presume there must be > some valid justification for not including an Apache License header in these > files. Just pointing it out now in case it really needs some attention and > has just escaped being noticed until now. Comments? I've certainly noticed them in the past... Machine generated files do not require license headers. So, IMO, these files are fine. I do have a question about the version #. IIUC, we are releasing 7.0.0 prior to the TC community. There may be fixes applied to the Tomcat dev tree prior to their 7.0 release. So, this release may not exactly match the functionality of the tomcat release. Is everyone evaluating that in their decision? --kevan
Re: [VOTE] Release Geronimo Customized Tomcat 7.0.0.0 (Second Try)
forget my +1 :-) 2010/5/5 Joe Bohn > > +1 (assuming the potential license issue mentioned below is not an issue) > > I was able to build and run the new tomcat image. > > The license issue pointed out last time is now resolved but there is one > other potential issue. I noticed a number of files under jasper-el that are > generated using JJTree & JavaCC and so have the following header but no > Apache license header. For example: > > /* Generated By:JJTree&JavaCC: Do not edit this line. ELParser.java */ > > Some other generated files include both a generated header and which is > immediately followed by the Apache license header. This seems a little > better to me. However, I see that we have released these without the Apache > header in earlier versions (and Tomcat as well) - so I presume there must be > some valid justification for not including an Apache License header in these > files. Just pointing it out now in case it really needs some attention and > has just escaped being noticed until now. Comments? > > Here is a list of the files that were flagged: > /jasper-el/src/main/java/org/apache/el/parser/ELParser.java > /jasper-el/src/main/java/org/apache/el/parser/ELParserConstants.java > /jasper-el/src/main/java/org/apache/el/parser/ELParserTokenManager.java > /jasper-el/src/main/java/org/apache/el/parser/ELParserTreeConstants.java > /jasper-el/src/main/java/org/apache/el/parser/JJTELParserState.java > /jasper-el/src/main/java/org/apache/el/parser/ParseException.java > /jasper-el/src/main/java/org/apache/el/parser/SimpleCharStream.java > /jasper-el/src/main/java/org/apache/el/parser/Token.java > /jasper-el/src/main/java/org/apache/el/parser/TokenMgrError.java > > Joe > > > > On 5/4/10 5:10 AM, Ivan wrote: > >> Please vote for Geronimo Customized Tomcat 7.0.0.0 >> >> 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-002/ >> >> Source repo: >> >> >> https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.0.0/ >> >> -- >> >> I have run the servlet/JSP TCK, at least, it does not bring new failures. >> >> The codes until rev 940711 are merged from Tomcat 7.0 trunk. >> >> About the java source codes with license issues found in the last vote, >> they are removed in the current code base from Geronimo side, as they >> are not required. >> -- >> Ivan >> > > -- Ivan
Re: Where is source tree for geronimo-txmanager-parent 3.0-SNAPSHOT?
On 5/5/2010 8:12 AM, Joe Bohn wrote: On 5/5/10 6:45 AM, Rick McGuire wrote: Doing some last minute dependency checking on the components. I see that the txmanager components have a parent pom of geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this version anywhere in the svn tree. The last version in tags is 2.1.4 and there is nothing in trunk for this. What am I missing here? Rick I see it in the root pom under trunk: https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk/pom.xml Joe Thanks! That solved another mystery. I couldn't figure out why the tags only had entries for the transaction parent. I should have expanded the directory. Rick
Re: Use slf4j api in all the xbean components and slf4j-api as the depdency ?
I am working on the ASM-based BundleClassFinder, if possible, I hope to include it in the coming XBean 3.7 release. Currently, most codes are done, and I am running some cases against it ! 2010/5/5 Rick McGuire > On 5/5/2010 3:03 AM, Ivan wrote: > >> Hi, >> I found that currently in xbean components, many log apis are used, >> slf4j, commons-logging, and log4j. I would like to use slf4j api everywhere. >> Also, I think that we could depend on slf4j-api directly, as not all the >> components need to run in OSGI environment. >> Thoughts ? If no objection, I would go ahead to change it. >> -- >> Ivan >> > I don't have a problem with that, other than requesting that you hold off > on making the change until after the new release of xbean has been released > for the Geronimo 3.0 milestone. > > Rick > -- Ivan
Re: Where is source tree for geronimo-txmanager-parent 3.0-SNAPSHOT?
On 5/5/10 6:45 AM, Rick McGuire wrote: Doing some last minute dependency checking on the components. I see that the txmanager components have a parent pom of geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this version anywhere in the svn tree. The last version in tags is 2.1.4 and there is nothing in trunk for this. What am I missing here? Rick I see it in the root pom under trunk: https://svn.apache.org/repos/asf/geronimo/components/txmanager/trunk/pom.xml Joe
[BUILD] branches/2.2: Failed for Revision: 941255
Geronimo Revision: 941255 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/build-0800.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20100505/unit-test-reports
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/ws/security/wss4j/1.5.8/wss4j-1.5.8.jar
316K downloaded
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/apache/santuario/xmlsec/1.4.3/xmlsec-1.4.3.jar
437K downloaded
Downloading:
http://maven.rtp.raleigh.ibm.com/nexus-proxy//org/bouncycastle/bcprov-jdk15/1.43/bcprov-jdk15-1.43.jar
1594K downloaded
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile]
[INFO] Compiling 19 source files to
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/classes
[INFO] [resources:testResources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/2.2/plugins/cxf/geronimo-cxf/target/geronimo-cxf-2.2.1-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-cxf/2.2.1-SNAPSHOT/geronimo-cxf-2.2.1-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, CXF :: CXF
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Added dependencies are saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.added.xml
Tree listing is saved here:
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/2.2/plugins/cxf/cxf/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycl
Re: Where is source tree for geronimo-txmanager-parent 3.0-SNAPSHOT?
On 5/5/2010 6:45 AM, Rick McGuire wrote: Doing some last minute dependency checking on the components. I see that the txmanager components have a parent pom of geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this version anywhere in the svn tree. The last version in tags is 2.1.4 and there is nothing in trunk for this. What am I missing here? And looking at the version that got pulled from the snapshot repo, the connector spec dependency in here really should be updated to the latest released version. Rick
Where is source tree for geronimo-txmanager-parent 3.0-SNAPSHOT?
Doing some last minute dependency checking on the components. I see that the txmanager components have a parent pom of geronimo-txmanager-parent 3.0-SNAPSHOT, but I can't seem to find this version anywhere in the svn tree. The last version in tags is 2.1.4 and there is nothing in trunk for this. What am I missing here? Rick
[jira] Updated: (GERONIMO-5153) Update CXF stack to version 2.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-5153: -- Fix Version/s: 2.2.2 (was: 3.0) (was: 2.2.1) Won't upgrade cxf to 2.2.6 in geronimo 2.2.1 > Update CXF stack to version 2.2.6 > - > > Key: GERONIMO-5153 > URL: https://issues.apache.org/jira/browse/GERONIMO-5153 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices >Affects Versions: 2.2 > Environment: All >Reporter: Alexandros Karypidis > Fix For: 2.2.2 > > Original Estimate: 24h > Remaining Estimate: 24h > > CXF has recently released versions 2.1.9 and 2.2.6. According to the project > lead, the 2.1 line will now be phased out (Geronimo uses 2.1.4). Therefore > Geronimo should consider switching to 2.2.6 for the future. > Reasons for this to occur immediately: > 1) CXF 2.2.6 is being advertized as one of the most stable versions to date: > http://www.dankulp.com/blog/?p=182 > http://mail-archives.apache.org/mod_mbox/cxf-users/201001.mbox/%3c201001251424.59438.dk...@apache.org%3e > 2) It appears to be a one -line change. I am totally inexperienced with > Geronimo (a new user) that ran into some issues and decided to try the update > myself on the 2.2 branch. I succeeded with just changing the "cxfVersion" > property of the top-level POM and re-building. See: > http://marc.info/?l=geronimo-user&m=126676750031858&w=2 > Here's the change: > C:\g22>svn diff pom.xml plugins\cxf\cxf\src\main\history\dependencies.xml > Index: pom.xml > === > --- pom.xml (revision 912260) > +++ pom.xml (working copy) > @@ -67,7 +67,7 @@ > 3.1.2 > 10.5.3.0_1 > - 2.1.4 > + 2.2.6 > 1.5 > 1.2.8 > 2.5.6 > Index: plugins/cxf/cxf/src/main/history/dependencies.xml > === > --- plugins/cxf/cxf/src/main/history/dependencies.xml (revision 912260) > +++ plugins/cxf/cxf/src/main/history/dependencies.xml (working copy) > @@ -111,4 +111,9 @@ > wss4j > jar > > + > + org.bouncycastle > + bcprov-jdk15 > + jar > + > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Use slf4j api in all the xbean components and slf4j-api as the depdency ?
On 5/5/2010 3:03 AM, Ivan wrote: Hi, I found that currently in xbean components, many log apis are used, slf4j, commons-logging, and log4j. I would like to use slf4j api everywhere. Also, I think that we could depend on slf4j-api directly, as not all the components need to run in OSGI environment. Thoughts ? If no objection, I would go ahead to change it. -- Ivan I don't have a problem with that, other than requesting that you hold off on making the change until after the new release of xbean has been released for the Geronimo 3.0 milestone. Rick
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: (was: GERONIMO-5273.patch) > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: GERONIMO-5273.patch > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- 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: 941172
Geronimo Revision: 941172 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 43 minutes 37 seconds
[INFO] Finished at: Wed May 05 03:44:55 EDT 2010
[INFO] Final Memory: 571M/1004M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100505/logs-0300-tomcat/
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.454 sec <<<
FAILURE!
[INFO] [failsafe:integration-test {execution: integration-test}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/enterprise-testsuite/appname-tests/appname-ear/target/failsafe-reports
---
T E S T S
---
Running TestSuite
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.454 sec <<<
FAILURE!
Results :
Failed tests:
testAppNameInjection(org.apache.geronimo.testsuite.appname.ServletTest)
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
[INFO] [geronimo:undeploy-module {execution: undeploy}]
[INFO] Using non-artifact based module id:
org.apache.geronimo.testsuite/appname-ear/3.0-SNAPSHOT/ear
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
Parsing URI=deployer:geronimo:jmx://localhost:1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
Parsing URI=deployer:geronimo:jmx://localhost:1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] : Using
protocol=jmx, host=localhost, port=1099
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] : Using
JMXServiceURL with host=localhost, port=1099, secure=false
[org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory] :
throwing
javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException:
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]
at
org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.newRemoteDeploymentManager(BaseDeploymentFactory.java:193)
at
org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory.getDeploymentManager(BaseDeploymentFactory.java:140)
at
javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManager.java:111)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.getDeploymentManager(ModuleMojoSupport.java:91)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.stopModule(ModuleMojoSupport.java:275)
at
org.apache.geronimo.mavenplugins.geronimo.module.ModuleMojoSupport.undeployModule(ModuleMojoSupport.java:309)
at
org.apache.geronimo.mavenplugins.geronimo.module.UndeployModuleMojo.doExecute(UndeployModuleMojo.java:37)
at
org.apache.geronimo.mavenplugins.geronimo.reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:99)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
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.j
[jira] Closed: (GERONIMO-5276) JavaEE6 sample - EJB 3.1 - Timer Service
[ https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5276. - Fix Version/s: 3.0 Resolution: Fixed Committed revision 941190. Thank you for this sample patch! > JavaEE6 sample - EJB 3.1 - Timer Service > > > Key: GERONIMO-5276 > URL: https://issues.apache.org/jira/browse/GERONIMO-5276 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia > Fix For: 3.0 > > Attachments: jira-5276.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4977) EN/Simp.Chinese UI information improvement for Console
[ https://issues.apache.org/jira/browse/GERONIMO-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864222#action_12864222 ] Kan Ogawa commented on GERONIMO-4977: - Shawn, Please close this issue for the time being. I will create new issue for the Japanese translation updates in this JIRA. Thanks, Kan Ogawa > EN/Simp.Chinese UI information improvement for Console > -- > > Key: GERONIMO-4977 > URL: https://issues.apache.org/jira/browse/GERONIMO-4977 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Reporter: Chi Runhua >Assignee: Shawn Jiang >Priority: Minor > Fix For: 2.2.1, 3.0 > > Attachments: UI_review_2.2.1.patch > > > There are lots of typos and inaccurate translation of UI information in the > Console. We did a thorough review and update those strings as much as we can. > The strings are mostly from .properties files under /i18n-resources directory > of each portlet as well as some .jsp fils within it. > Please help with review and commit the patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5276) JavaEE6 sample - EJB 3.1 - Timer Service
[ https://issues.apache.org/jira/browse/GERONIMO-5276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guang Zhe Wang updated GERONIMO-5276: - Attachment: (was: jira-5276.patch) > JavaEE6 sample - EJB 3.1 - Timer Service > > > Key: GERONIMO-5276 > URL: https://issues.apache.org/jira/browse/GERONIMO-5276 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: (was: GERONIMO-5273.patch) > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5273) JavaEE6 sample - EJB 3.1 - Singleton
[ https://issues.apache.org/jira/browse/GERONIMO-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tang Yin Qi updated GERONIMO-5273: -- Attachment: GERONIMO-5273.patch > JavaEE6 sample - EJB 3.1 - Singleton > > > Key: GERONIMO-5273 > URL: https://issues.apache.org/jira/browse/GERONIMO-5273 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Forrest Xia >Assignee: Forrest Xia > Attachments: GERONIMO-5273.patch, GERONIMO-5273.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4977) EN/Simp.Chinese UI information improvement for Console
[ https://issues.apache.org/jira/browse/GERONIMO-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864218#action_12864218 ] Shawn Jiang commented on GERONIMO-4977: --- Closing this JIRA. Kan, Do you still want to make the Japanese translation for the updates in this JIRA ? you could open a new JIRA to track this task if you want. > EN/Simp.Chinese UI information improvement for Console > -- > > Key: GERONIMO-4977 > URL: https://issues.apache.org/jira/browse/GERONIMO-4977 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Reporter: Chi Runhua >Assignee: Shawn Jiang >Priority: Minor > Fix For: 2.2.1, 3.0 > > Attachments: UI_review_2.2.1.patch > > > There are lots of typos and inaccurate translation of UI information in the > Console. We did a thorough review and update those strings as much as we can. > The strings are mostly from .properties files under /i18n-resources directory > of each portlet as well as some .jsp fils within it. > Please help with review and commit the patch. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4238) JMX over SSL improvements
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang closed GERONIMO-4238. - Fix Version/s: 2.1.5 Resolution: Fixed #2 #3 were fixed. #1 is a duplicate of https://issues.apache.org/jira/browse/GERONIMO-5148 > JMX over SSL improvements > - > > Key: GERONIMO-4238 > URL: https://issues.apache.org/jira/browse/GERONIMO-4238 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: general >Affects Versions: 2.1.2, 2.2 >Reporter: Jarek Gawor >Assignee: Shawn Jiang > Fix For: 2.2.1, 2.1.5 > > Attachments: 4238#1.trunk.patch, G4238_g21.patch > > > 1) After the non-secure JMX server is disabled, the server won't start up > because the org.apache.geronimo.configs/clustering module fails to find the > JMX server. Not sure why the clustering module needs the JMX server in the > first place but we should allow the server to work ok with a secure JMX > server. > 2) Shutdown command needs to support --secure option. > 3) Test if gshell start-server/stop-server work ok with a secure JMX server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Use slf4j api in all the xbean components and slf4j-api as the depdency ?
Hi, I found that currently in xbean components, many log apis are used, slf4j, commons-logging, and log4j. I would like to use slf4j api everywhere. Also, I think that we could depend on slf4j-api directly, as not all the components need to run in OSGI environment. Thoughts ? If no objection, I would go ahead to change it. -- Ivan
