[BUILD] branches/2.1: Failed for Revision: 926939

Geronimo Revision: 926939 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100324/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100324/unit-test-reports

Re: [BUILD] branches/2.1: Failed for Revision: 926939

should be fixed 2010/3/24 ga...@apache.org Geronimo Revision: 926939 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100324/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo

[BUILD] trunk: Failed for Revision: 926954

Geronimo Revision: 926954 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/unit-test

[jira] Commented: (GERONIMO-5204) var/security/keystores seems to be a required directory, but is not being created for custom assemblies

[ https://issues.apache.org/jira/browse/GERONIMO-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849100#action_12849100 ] Rex Wang commented on GERONIMO-5204: This is not caused by the recent keystore

[jira] Issue Comment Edited: (GERONIMO-5204) var/security/keystores seems to be a required directory, but is not being created for custom assemblies

[ https://issues.apache.org/jira/browse/GERONIMO-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849100#action_12849100 ] Rex Wang edited comment on GERONIMO-5204 at 3/24/10 8:37 AM: -

[jira] Reopened: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo

[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reopened GERONIMO-5129: revert the changes in rev.923622 rev.923649 for this jira @ rev.926985 reference:

[jira] Updated: (GERONIMO-5129) Fix to be picked from tomcat for Spnego support in geronimo

[ https://issues.apache.org/jira/browse/GERONIMO-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5129: --- Fix Version/s: (was: 2.1.5) Wish List Fix to be picked from tomcat for

[jira] Closed: (GERONIMO-5204) var/security/keystores seems to be a required directory, but is not being created for custom assemblies

[ https://issues.apache.org/jira/browse/GERONIMO-5204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-5204. -- Resolution: Fixed rev.926980 for branch 2.1 rev.926991 for branch 2.2 var/security/keystores

[BUILD] branches/2.2: Failed for Revision: 927017

Geronimo Revision: 927017 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100324/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100324/unit-test-reports

Re: svn commit: r926991 - /geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml

Thanks Rex. Makes sense. I guess that's consistent with our treatment of server-security-config dependencies, but I'm not convinced we're handling them correctly. Pretty certain that we can build alternate assemblies with the same basic problem... --kevan On Mar 24, 2010, at 5:40 AM,

[BUILD] trunk: Failed for Revision: 927043

Geronimo Revision: 927043 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/unit-test

shared lib in Geronimo 3.0

My apologies if this has been discussed before, but what is the thinking on the shared lib on Geronimo 3.0? As Geronimo moves to the OSGi based infrastructure, will it make it into G 3.0? If so, how would it be exposed in terms of classloading? Thanks... Sangjin

Re: shared lib in Geronimo 3.0

On Mar 24, 2010, at 9:20 AM, Sangjin Lee wrote: My apologies if this has been discussed before, but what is the thinking on the shared lib on Geronimo 3.0? As Geronimo moves to the OSGi based infrastructure, will it make it into G 3.0? If so, how would it be exposed in terms of

Re: shared lib in Geronimo 3.0

Thanks. So it sounds like it will be pretty much a *requirement* that applications on 3.0 need to be fully OSGi bundles, and if you were using the shared lib as part of your classloading scheme you will have to convert them all to OSGi bundles. Regards, Sangjin On Wed, Mar 24, 2010 at 11:56 AM,

[jira] Created: (GERONIMO-5205) Integrate Aries JPA OSGi component and blueprint extensions

Integrate Aries JPA OSGi component and blueprint extensions --- Key: GERONIMO-5205 URL: https://issues.apache.org/jira/browse/GERONIMO-5205 Project: Geronimo Issue Type: Sub-task

build failed in branches/2.2

Hi I am a newbi at building geronimo so it could be by lack of knowledge,in that case forgive me. I am trying to build the 2.2 branch from source. I am at the latest revision (927171) and followed the instructions at http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html I started

[jira] Commented: (GERONIMO-5205) Integrate Aries JPA OSGi component and blueprint extensions

[ https://issues.apache.org/jira/browse/GERONIMO-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12849414#action_12849414 ] Jarek Gawor commented on GERONIMO-5205: --- I updated the openejb2 plugin to install

Re: shared lib in Geronimo 3.0

On Mar 24, 2010, at 12:58 PM, Sangjin Lee wrote: Thanks. So it sounds like it will be pretty much a *requirement* that applications on 3.0 need to be fully OSGi bundles, Well, the idea is that the geronimo deployment process will turn your javaee app into one or more bundles. We set up

Re: build failed in branches/2.2

to rebuild successfully. I also see the automated build ran successfully -- http://people.apache.org/builds/geronimo/server/binaries/2.2/20100324/build-1400.log The sha checksum of my geronimo-connector-2.1.4.jar is fa36907547ad3239128a76d515d83fa3ba4f2ff4 which matches http://repo2.maven.org/maven2

Re: shared lib in Geronimo 3.0

On Mar 24, 2010, at 4:57 PM, David Jencks wrote: On Mar 24, 2010, at 12:58 PM, Sangjin Lee wrote: Thanks. So it sounds like it will be pretty much a *requirement* that applications on 3.0 need to be fully OSGi bundles, Well, the idea is that the geronimo deployment process will turn

Re: shared lib in Geronimo 3.0

On Mar 24, 2010, at 2:10 PM, Kevan Miller wrote: On Mar 24, 2010, at 4:57 PM, David Jencks wrote: On Mar 24, 2010, at 12:58 PM, Sangjin Lee wrote: Thanks. So it sounds like it will be pretty much a *requirement* that applications on 3.0 need to be fully OSGi bundles, Well, the

RE: build failed in branches/2.2

://people.apache.org/builds/geronimo/server/binaries/2.2/20100324/bu ild-1400.log The sha checksum of my geronimo-connector-2.1.4.jar is fa36907547ad3239128a76d515d83fa3ba4f2ff4 which matches http://repo2.maven.org/maven2/org/apache/geronimo/components/geronimo-co nnector/2.1.4/geronimo

Re: shared lib in Geronimo 3.0

I wholeheartedly agree that if you're going to be in the OSGi runtime the shared lib approach doesn't make sense. You would be denying yourself all the benefits that OSGi brings in terms of classloading and flexibility. I just wanted to be clear that at a high level in 3.0 OSGi is not only a

Re: shared lib in Geronimo 3.0

On Mar 24, 2010, at 5:30 PM, David Jencks wrote: While I always thought shared lib was a bad idea, at least pre-osgi the concept of a classloader that you could just toss things in made sense. I don't think it makes any sense in osgi. There is no dynamic-export header so whatever

[jira] Closed: (GERONIMO-4957) javax.el.CompositeELResolver is not thread-safe

[ https://issues.apache.org/jira/browse/GERONIMO-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-4957. -- Resolution: Fixed Fix Version/s: 2.2.1 2.1.5

[BUILD] trunk: Failed for Revision: 927249

Geronimo Revision: 927249 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100324/unit-test

Remove Stax API or wstx-asl ?

Hi, Just trying the latest Geronimo 3.0 build, get a CNF exception for the XMLInputFactory, seems that wstx-asl shipped is not a bundle. I am thinking that since JRE 1.6 contains the API and the default implementation, do we still need to ship another one ? -- Ivan

Re: svn commit: r926991 - /geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml

Yes, I agree. How about merge server-security-config car into j2ee-security(actually I think we should rename the car as server-security)? Will open a jira to track this. 2010/3/24 Kevan Miller kevan.mil...@gmail.com Thanks Rex. Makes sense. I guess that's consistent with our treatment of

[VOTE] Release tomcat-parent-6.0.26

This voting is for tomcat-parent-6.0.26. It will be used by Geronimo 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we also applied some patches which haven't been included in tomcat 6.0.26. Based on tomcat 6.0.26 tag, we applied additional patches for GERONIMO-3451 -

Re: [VOTE] Release tomcat-parent-6.0.26

TCK for tomcat-parent-6.0.26 is ongoing. Ivan, could you give the result here once TCK is completed? Thanks in advance! 2010/3/25 Delos dait...@gmail.com This voting is for tomcat-parent-6.0.26. It will be used by Geronimo 2.1.5.It's based on tomcat 6.0.26, built with maven. Besides, we

[jira] Updated: (GERONIMO-5206) Assembly may start failed when server-security-config car is not assembled

[ https://issues.apache.org/jira/browse/GERONIMO-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang updated GERONIMO-5206: --- Affects Version/s: 2.2.1 Assembly may start failed when server-security-config car is not

[jira] Created: (GERONIMO-5206) Assembly may start failed when server-security-config car is not assembled

Assembly may start failed when server-security-config car is not assembled -- Key: GERONIMO-5206 URL: https://issues.apache.org/jira/browse/GERONIMO-5206 Project: Geronimo

Re: Remove Stax API or wstx-asl ?

On Wednesday 24 March 2010 9:44:12 pm Ivan wrote: Hi, Just trying the latest Geronimo 3.0 build, get a CNF exception for the XMLInputFactory, seems that wstx-asl shipped is not a bundle. I am thinking that since JRE 1.6 contains the API and the default implementation, do we still need

can't start framework assembly

Rick, With the recent spec updates I'm unable to start a framework assembly. Maybe I have some old snapshot somewhere but here's what I see when I start the framework: Bundle listed in startup.properties configuration not found: