[ANNOUNCE] Alan Cabrera has been appointed as the new PMC Chair of the Geronimo Project
All, Due to lack of time, in the last few months, I've found it very difficult to contribute and stay on top of Geronimo activities. So, last month I informed the PMC that I would like to step down as the PMC Chair of the Geronimo Project. The Geronimo PMC nominated Alan Cabrera to become the new PMC Chair. Today, I'm happy to announce that the ASF Board (at this month's meeting) officially appointed Alan to be the new PMC Chair of the Geronimo Project. Congratulations Alan! Jarek p.s. To all the PMC members, committers, contributors, and users that made my life easier as PMC chair - thank you!
Re: Board report time
Yep. I updated the board report & submitted it. Thanks! On Mon, Feb 16, 2015 at 2:13 AM, Romain Manni-Bucau wrote: > Hello Jarek, > > we can say we released some spec jars + javamail as well > > > Romain Manni-Bucau > @rmannibucau > http://www.tomitribe.com > http://rmannibucau.wordpress.com > https://github.com/rmannibucau > > > 2015-02-16 6:34 GMT+01:00 Jarek Gawor : >> I'll submit this tomorrow. Any last minute updates? >> >> Jarek >> >> On Tue, Feb 3, 2015 at 2:16 PM, Jarek Gawor wrote: >>> Hi all, >>> >>> Since I forgot to create a board report for January we have to provide >>> one for February. Here's my initial draft: >>> >>> https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-02+-+February >>> >>> If I missed something please let me know or go ahead and update the >>> page directly. >>> >>> Thanks, >>> Jarek
Re: Board report time
I'll submit this tomorrow. Any last minute updates? Jarek On Tue, Feb 3, 2015 at 2:16 PM, Jarek Gawor wrote: > Hi all, > > Since I forgot to create a board report for January we have to provide > one for February. Here's my initial draft: > > https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-02+-+February > > If I missed something please let me know or go ahead and update the > page directly. > > Thanks, > Jarek
Board report time
Hi all, Since I forgot to create a board report for January we have to provide one for February. Here's my initial draft: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2015-02+-+February If I missed something please let me know or go ahead and update the page directly. Thanks, Jarek
Board report time
Hi all, This is a bit late but I created a draft board report for October: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2014-10+-+October If I missed something please let me know or go ahead and update the page directly. Thanks, Jarek
Re: [VOTE] geronimo javamail 1.8.4
+1 Jarek On Sun, Jul 20, 2014 at 3:40 AM, Romain Manni-Bucau wrote: > Hi guys > > I'd like to call a vote for geronimo javamail 1.8.4 > > It mainly fixes a bug for pop3 protocol where INBOX was replaced by INPUT in > our code (https://issues.apache.org/jira/browse/GERONIMO-6523) > > Here is the staging repo: > https://repository.apache.org/content/repositories/orgapachegeronimo-1002/ > > vote will be opened for 3 days or until 3 pmc votes are obtained as usually. > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau
Re: [VOTE] geronimo javamail 1.8.4
Can you add it to https://svn.apache.org/repos/asf/geronimo/KEYS? Instructions are in the file. Jarek On Mon, Jul 21, 2014 at 5:28 PM, Romain Manni-Bucau wrote: > Hi > > No that's true, here it is: > > > pub 2048R/3134B697 2014-03-29 > uid Romain Manni-Bucau > sig 33134B697 2014-03-29 Romain Manni-Bucau > > sub 2048R/880A5772 2014-03-29 > sig 3134B697 2014-03-29 Romain Manni-Bucau > > > -BEGIN PGP PUBLIC KEY BLOCK- > Version: GnuPG v1 > > mQENBFM3IdUBCACbx+yPu1PiSg/9F06Yi9aiLhHDCM5N4RZ+UCSXdOJ8Ot7d5DuS > +sQGNJdMD3AQRzZnQzfwyTsDSsYVbRI+I6stRwqps89tTrI385SRai4VFbJIcpXf > +UMTm+BHo2NWH6IiS5wTKF8Exl4iEuAdIdj8a6Cned5VoXhH7A7/PPjd0eljcbwD > rhpG9dCe/HlFOoEfgUTn4MjiZHNbOvbGAhWoUYmf1+K2uqOqIz4ISngGsxAZGvjV > kGfscVczgx2guO210DAGu7m46faoxJEus9qMGRS8NvRJpqpgKbSDxskTUygDESBR > UVMfKcAUeDbqmgMcOea5uP1L+KxHaW0wB3tNABEBAAG0K1JvbWFpbiBNYW5uaS1C > dWNhdSA8cm1hbm5pYnVjYXVAYXBhY2hlLm9yZz6JATgEEwECACIFAlM3IdUCGwMG > CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEDaQ4CIxNLaXhvEH/3G+G677SAXi > CMtxuzWgI1g0m33VViCXgTg7bF0TaF7BxHa+stt9WSUGz4h1Dqf23dzjfW+WMWnB > 1Akd+ClXhrO9Yu8EFUvWyOf5lHNqpUqRX1ea+0TeTQbjWxIaCXcBxrkfjFxEbQpN > fOwzLYWZBNSJu/QeWftPYLzhvBukSGctAPXhQJYa3bVYQpVZHpYDW1xFTDOqxzWL > htPNIFc3ITCO2+zqON9mFgBU9C1shZBWYpx3oK6OXtbRg6bFBSlNCV4jg0P6QaOZ > Gs/tu3gCMZrV4mOqajTgHzJnIs2hszrkJb5ONQaeUVTLqqQgkLZ3dMEAhUC87L7n > FIDmFwjMWC25AQ0EUzch1QEIAMTtQx+iZ24XetAKSGh2jD+kqudr7vKcs5tPFE8w > CsiMkbwFlagP/jRtwSIJVHutfXzhu45D2dPWfUKnECM8byuIJr0hwGzpx+w0CmHb > NcAT8ixUmNE3WLiQfDCqtrvlx409qKa8wUjMMsjshQ2JaUpOs728os9awowFj56A > li0FIW1prgvtDaZ5dP8hXb2Uo52kEgPfhWlqm5lHe63KU7LXxfD1iNBwElMDtCQ3 > VX8m7FSJ+JyUEoflz8DaXnpW4tdGBcLZoUrXsuF8FkDgFBwRtYIQQ57OUE4VUhDr > Yl8QJvylyJoviCsMaYWmIpWjUKMfqjSTH82Tajk9/LSQYt8AEQEAAYkBHwQYAQIA > CQUCUzch1QIbDAAKCRA2kOAiMTS2lwg2CACaFFTFeKNDwo2OHHkKWUdSKz3h55ek > AGWTMvTCv5kR71PFMD4NVW3MBt9gdfCTLcV8w5ZeJChMOJKKH58p4aIuM93TvqCG > pRicpkv/ENnp/JCvud0zIcQRHJEb17mmHb5xyllprpX3Tqv35vtd1ApOhfJn30F0 > MgP4zaEojybuvzHEAVAbzj6+WsGXiXesMvVrXekpVAw1lpljZ/pHfzD9ivz3I9g1 > wGR0hO+gPPlL0HrfvbElARwc2I9GC1nniLD5nuIOuVx91D/zu61BuVsZCo9dPMat > g4Bme6JQ26eG0gZOj0JhjESDej9MFYGBtEFcisRw+UZhcT7v2YXxsm54 > =kE/0 > -END PGP PUBLIC KEY BLOCK- > > Should be in openejb but not geronimo (BTW if you have a tip to checkout > this file without checkout all the geronimo tree it would be welcomed) > > > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-07-21 21:16 GMT+02:00 Alan Cabrera : > >> Is your PGP key in https://svn.apache.org/repos/asf/geronimo/KEYS? I >> can’t get the signatures to verify. >> >> >> Regards, >> Alan >> >> >> On Jul 20, 2014, at 12:40 AM, Romain Manni-Bucau >> wrote: >> >> Hi guys >> >> I'd like to call a vote for geronimo javamail 1.8.4 >> >> It mainly fixes a bug for pop3 protocol where INBOX was replaced by INPUT >> in our code (https://issues.apache.org/jira/browse/GERONIMO-6523) >> >> Here is the staging repo: >> https://repository.apache.org/content/repositories/orgapachegeronimo-1002/ >> >> vote will be opened for 3 days or until 3 pmc votes are obtained as >> usually. >> >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >
Re: javaee 7 binaries?
No, we don't. But if it's something you could help with that would be great! Although, does anyone remember whether if we can release a spec jar for a final spec that has not passed (or has not been validated yet with) the TCK signature tests? I think we had some conversations about it in the past but can't find the right emails in my archive. Jarek On Sat, Jul 5, 2014 at 3:21 PM, Romain Manni-Bucau wrote: > Hello guys, > > any plan to release (even in alpha since we don't valid signatures > against TCKs) javaee 7 artifacts? > > I'm thinking in particular about: > > 1) concurrency utilities for ee > 2) json processing > > maybe cdi 1.1, interceptors 1.2 too. > > wdyt? > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau
Board report time
Hi all, Sorry, it's a bit late but I created a draft board report for July: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2014-07+-+July If I missed something please let me know or go ahead and update the page directly. The report is due on the 9th (Wednesday). Thanks, Jarek
Board Report Time
Hi all, I created a draft board report for April: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2014-04+-+April If I missed something please let me know or go ahead and update the page directly. The report is due on the 9th (Wednesday). Thanks, Jarek
Re: [VOTE] XBean 3.17
+1 Jarek On Mon, Mar 31, 2014 at 3:54 PM, Romain Manni-Bucau wrote: > Hi, > > I'm starting a vote for an xbean 3.17 release. > > The main change is the removing of asm3 and 4 shades and the > replacement with asm5 one to be able to be compatible with java 8. > > Binaries: > > https://repository.apache.org/content/repositories/orgapachegeronimo-1000/ > (yeah this number is awesome ;)) > > Tag: > > http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.17/ > > Hope I didn't do something wrong since I'm not yet really familiar > with releases. > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867017#comment-13867017 ] Jarek Gawor commented on GERONIMO-6451: --- I fixed the comma. The new snaphost is published at: http://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-jpa_2.1_spec/1.0-SNAPSHOT/. > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0-src.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, > jpa2.1-src.patch.txt > > > Updated JPA 2.1 jar for Java EE 7. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: Board Report Time
Last chance to review / update the draft. I will publish it later today. Thanks, Jarek On Mon, Jan 6, 2014 at 11:22 AM, Jarek Gawor wrote: > Sorry, it's a bit late but I created a draft board report for January: > https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2014-01+-+January > > If I missed something please let me know or go ahead and update the > page directly. > > The report is due on the 8th (Wednesday). > > Jarek
Board Report Time
Sorry, it's a bit late but I created a draft board report for January: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2014-01+-+January If I missed something please let me know or go ahead and update the page directly. The report is due on the 8th (Wednesday). Jarek
Re: [VOTE] Release stax-api-1.2 spec v 1.2
+1 Jarek On Wed, Nov 27, 2013 at 11:04 AM, Guillaume Nodet wrote: > I've uploaded a release at > https://repository.apache.org/content/repositories/orgapachegeronimo-014/ > to fix the following issue: > https://issues.apache.org/jira/browse/GERONIMO-6509 > > Please review and vote, > > Cheers, > Guillaume >
Re: [VOTE] XBean 3.16 release
+1 Jarek On Wed, Nov 13, 2013 at 5:14 PM, Guillaume Nodet wrote: > I'm starting a vote for an xbean 3.16 release. > The 3.15 of last week is unusable in OSGi due to some OSGi metadata > problems. > See https://issues.apache.org/jira/browse/XBEAN-258 > > Binaries: > > https://repository.apache.org/content/repositories/orgapachegeronimo-130/ > > Tag: > > http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.16/ > > Please review and vote. > > > -- > --- > Guillaume Nodet > > Red Hat, Open Source Integration > > Email: gno...@redhat.com > Web: http://fusesource.com > Blog: http://gnodet.blogspot.com/ >
Re: [VOTE] XBean 3.15 release
+1 Jarek On Wed, Nov 6, 2013 at 11:55 PM, David Blevins wrote: > Ok, release rolled! > > Binaries: > > https://repository.apache.org/content/repositories/orgapachegeronimo-086/ > > Tag: > > http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.15/ > > > 72 hours for voting! :) > > > -David >
[jira] [Resolved] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6507. --- Resolution: Fixed Should be all fixed now. > Various code samples not visible > > > Key: GERONIMO-6507 > URL: https://issues.apache.org/jira/browse/GERONIMO-6507 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 3.0.0 >Reporter: Peter Lynch >Assignee: Jarek Gawor >Priority: Minor > > As per related defect GERONIMO-6506, there are a number of documentation > pages that do not display all code samples. Here is a list: > ||Page title||URL|| > |Replacing default Realm in > Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| > |Database (SQL) > Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| > |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| > |Configuring Virtual Host in > Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| > |Monitoring thread > pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| > |Creating deployment plans for EJB > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| > |Creating deployment plans for enterprise > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| > |Creating deployment plans for Java EE application > clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| > |Creating deployment plans for Java Persistence > API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| > |Developing container managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| > |Developing bean managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| > |Developing persistence for JSF applications with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| > |Deploying and running JPA application > client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| > |Developing Web > services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813984#comment-13813984 ] Jarek Gawor commented on GERONIMO-6507: --- Most of them should be fixed now but I just checked and I think I missed a couple in the first round. Remaining updates should be publishing a few hours. > Various code samples not visible > > > Key: GERONIMO-6507 > URL: https://issues.apache.org/jira/browse/GERONIMO-6507 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 3.0.0 >Reporter: Peter Lynch >Assignee: Jarek Gawor >Priority: Minor > > As per related defect GERONIMO-6506, there are a number of documentation > pages that do not display all code samples. Here is a list: > ||Page title||URL|| > |Replacing default Realm in > Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| > |Database (SQL) > Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| > |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| > |Configuring Virtual Host in > Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| > |Monitoring thread > pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| > |Creating deployment plans for EJB > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| > |Creating deployment plans for enterprise > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| > |Creating deployment plans for Java EE application > clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| > |Creating deployment plans for Java Persistence > API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| > |Developing container managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| > |Developing bean managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| > |Developing persistence for JSF applications with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| > |Deploying and running JPA application > client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| > |Developing Web > services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-6507: - Assignee: Jarek Gawor > Various code samples not visible > > > Key: GERONIMO-6507 > URL: https://issues.apache.org/jira/browse/GERONIMO-6507 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 3.0.0 >Reporter: Peter Lynch >Assignee: Jarek Gawor >Priority: Minor > > As per related defect GERONIMO-6506, there are a number of documentation > pages that do not display all code samples. Here is a list: > ||Page title||URL|| > |Replacing default Realm in > Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| > |Database (SQL) > Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| > |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| > |Configuring Virtual Host in > Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| > |Monitoring thread > pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| > |Creating deployment plans for EJB > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| > |Creating deployment plans for enterprise > applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| > |Creating deployment plans for Java EE application > clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| > |Creating deployment plans for Java Persistence > API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| > |Developing container managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| > |Developing bean managed persistence with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| > |Developing persistence for JSF applications with > JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| > |Deploying and running JPA application > client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| > |Developing Web > services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| > |Extensible Administration > Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (GERONIMO-6506) Code samples not visible in "Developing a Simple JavaServer Faces application" tutorial
[ https://issues.apache.org/jira/browse/GERONIMO-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6506. --- Resolution: Fixed Assignee: Jarek Gawor Should be fixed now. Thanks! > Code samples not visible in "Developing a Simple JavaServer Faces > application" tutorial > --- > > Key: GERONIMO-6506 > URL: https://issues.apache.org/jira/browse/GERONIMO-6506 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 3.0.0 > Environment: Windows 7 Home Premium Service Pack 1 > Mozilla Firefox 24.0 > Internet Explorer 9.0.8112.16421 >Reporter: Peter Lynch >Assignee: Jarek Gawor >Priority: Minor > > When viewing the "Developing a Simple JavaServer Faces application" tutorial > (http://geronimo.apache.org/GMOxDOC30/developing-a-simple-javaserver-faces-application.html) > in either of the above browsers, several code samples are not displayed: > * login.jsp, welcome.jsp and 3 code snippets from login.jsp, all in the > section "Define and implement View (V) in application" > * index.jsp in the section "Define and implement the View navigation by > Controller (C)" > I notice that when I view this page, I receive what seem to be javascript > errors, stating "SyntaxHighlighter Can't find brush for: actionscript". This > message is displayed 6 times, perhaps corresponding to the 6 code samples > above. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: driver-downloads.properties problem
I updated the MySQL driver to version 5.1.26. Give it a try and see if it works for you now. Jarek On Fri, Oct 25, 2013 at 1:12 PM, Zsolt Dénes wrote: > Dear All! > > Thanks for your work, I really like geronimo! But, I would like to use it, > with mysql 5.1 jdbc driver, but in the (Database pool creating) wizzard > can't download the MySQL driver ver. 5.1.22 because the URL, from the > http://geronimo.apache.org/driver-downloads.properties doesn't correct. > > Is there any way, to read this property file from local, or read the url > from local property? Because for example, if the site down, I can not change > this config property :( I can override, compile nad repack it to the jar, > but I'm a java developer, not a system admin, or same like that :) > > Can You change the url resource of this property, or add the freshness > driver (5.1.26)? > > Thanks your work! > > Beast regards, > Zsolt Denes
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802946#comment-13802946 ] Jarek Gawor commented on GERONIMO-6451: --- It has not been released yet and therefore it's not available on Maven central. However, you can pick up a snaphost from the following location: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-jpa_2.1_spec/1.0-SNAPSHOT/ > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, > jpa2.1-src.patch.txt > > > Updated JPA 2.1 jar for Java EE 7. -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: geronimo-osgi-support pom question
These are dependencies only used by the tests (*-itests modules). They are not exported or used by geronimo-osgi-locator or geronimo-osgi-registry so it all should be ok. Jarek On Tue, Oct 15, 2013 at 1:33 PM, Mark Struberg wrote: > hi! > > the specs/geronimo-osgi-support has tons of stuff in it's > dependencyManagement section which it actually does not use at all. e.g. > org.ops4j stuff including some swisscom specific stuff. > Can we simply get rid of it? Who is using this anyway? It seems not to get > imported by any of the other geromino/specs projects. > > Can anyone shed a light on this? > > LieGrue, > strub
[jira] [Resolved] (GERONIMO-6505) CloseReason.CloseCodes enum's getCode method always returns 1111
[ https://issues.apache.org/jira/browse/GERONIMO-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6505. --- Resolution: Fixed Thanks for the patch. Committed it in revision 1531446. > CloseReason.CloseCodes enum's getCode method always returns > > > Key: GERONIMO-6505 > URL: https://issues.apache.org/jira/browse/GERONIMO-6505 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: specs >Reporter: Andy McCright >Assignee: Andy McCright >Priority: Minor > Attachments: patch-websockets-CloseReason.txt > > > The initial implementation of the websockets API has a mistake in the > implementation of the CloseCodes enum (in javax.websocket.CloseReason). When > calling the getCode() method, instead of returning the proper code for the > specified CloseReason (i.e. NORMAL_CLOSURE should return 1000, GOING_AWAY > should return 1001, etc.), it always returns . -- This message was sent by Atlassian JIRA (v6.1#6144)
Re: 3 important Geronimo Schema links broke. Please advise.
The first one should be fixed now. Jarek On Tue, Oct 8, 2013 at 4:52 AM, Zhi Xie wrote: > 1.http://geronimo.apache.org/xml/ns/deployment-1.2 > 2.http://openejb.apache.org/xml/ns/openejb-jar-2.2 > 3.http://openejb.apache.org/xml/ns/pkgen-2.1 > > The first link is redirected to geronimo-config-1.2.xsd. But could not find > the schema. > The last 2 links I have asked in openejb community. But currently the answer > is they have never published them. > > So does anyone have comments in the case? > > -- > Best Regards > Gary
Board Report Time
I created a draft board report for October: https://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2013-10+-+October If I missed something please let me know of update the page. The report is due on the 9th (Wednesday). Jarek
Re: [ANNOUNCE] Jarek Gawor has been appointed as the the PMC Chair of the Geronimo Project
Kevan, Thanks again for all your time & effort. You have been an excellent PMC chair and I have learned a lot from you. Thanks for your invaluable advice and expertise given to me and this project. Good luck! Thanks, Jarek On Tue, Jul 30, 2013 at 12:39 PM, Kevan Miller wrote: > All, > Due to recent changes in my life, I've had less and less time to devote to > the Geronimo project. Last month, I told the PMC that I wished to step down > from my PMC Chair duties. > > The Geronimo PMC unanimously nominated Jarek Gawor to become the PMC Chair. > I'm happy to announce that at this month's board meeting, the ASF Board > appointed Jarek the new PMC Chair of the Geronimo project. > > As anyone following the Geronimo project should know, Jarek has been bringing > a tremendous amount to the project in multiple ways. Please take a moment to > thank Jarek for taking on this new role. > > Finally, to all the PMC members, committers, contributors, and users -- > thanks for making my job as PMC chair so easy and enjoyable. It's been a > pleasure working with you. > > --kevan
[jira] [Resolved] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6453. --- Resolution: Fixed Committed your patch in revision 1505072. Thanks again! > API jar for JSR 340 - Servlet 3.1 > - > > Key: GERONIMO-6453 > URL: https://issues.apache.org/jira/browse/GERONIMO-6453 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter >Assignee: Andy McCright > Attachments: getVirtualServerName-patch.txt, patch.txt > > > Update jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6484) Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
[
https://issues.apache.org/jira/browse/GERONIMO-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-6484.
---
Resolution: Fixed
Assignee: Jarek Gawor
Committed the fix in revision 1504952.
> Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
> -
>
> Key: GERONIMO-6484
> URL: https://issues.apache.org/jira/browse/GERONIMO-6484
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Bert Jacobs
>Assignee: Jarek Gawor
>
> I'm using Karaf 2.3.2.
> The endorsed directory contains the ServiceMix
> org.apache.servicemix.specs.jaxb-api-2.2-2.2.0 bundle which in turn includes
> a shaded version of geronimo-activation_1.1_spec version 1.0.2.
> My code uses a FileDataSource, requests the content type and receives this:
> {noformat}
> Caused by: java.lang.NullPointerException
> at
> javax.activation.MimetypesFileTypeMap.(MimetypesFileTypeMap.java:62)[:2.2.0]
> at
> javax.activation.FileTypeMap.getDefaultFileTypeMap(FileTypeMap.java:53)[:2.2.0]
> at
> javax.activation.FileDataSource.getContentType(FileDataSource.java:69)[:2.2.0]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6484) Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
[
https://issues.apache.org/jira/browse/GERONIMO-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713902#comment-13713902
]
Jarek Gawor commented on GERONIMO-6484:
---
Btw, a snapshot should be published soon as
https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.2-SNAPSHOT/
> Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
> -
>
> Key: GERONIMO-6484
> URL: https://issues.apache.org/jira/browse/GERONIMO-6484
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
>Reporter: Bert Jacobs
>Assignee: Jarek Gawor
>
> I'm using Karaf 2.3.2.
> The endorsed directory contains the ServiceMix
> org.apache.servicemix.specs.jaxb-api-2.2-2.2.0 bundle which in turn includes
> a shaded version of geronimo-activation_1.1_spec version 1.0.2.
> My code uses a FileDataSource, requests the content type and receives this:
> {noformat}
> Caused by: java.lang.NullPointerException
> at
> javax.activation.MimetypesFileTypeMap.(MimetypesFileTypeMap.java:62)[:2.2.0]
> at
> javax.activation.FileTypeMap.getDefaultFileTypeMap(FileTypeMap.java:53)[:2.2.0]
> at
> javax.activation.FileDataSource.getContentType(FileDataSource.java:69)[:2.2.0]
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710220#comment-13710220 ] Jarek Gawor commented on GERONIMO-6481: --- I committed your patch with minor changes in revision 1503881. I updated the sshd and mina dependencies to match what Karaf wanted. Please double check things and thanks for the patch! > Karaf shell ssh bundle for IBM JDK SR10 host key issue > -- > > Key: GERONIMO-6481 > URL: https://issues.apache.org/jira/browse/GERONIMO-6481 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0.0, 3.0.1 >Reporter: xiezhi >Assignee: Andy McCright > Attachments: 6481-patch-2.txt, 6481-patch.txt > > > When you launch Geronimo Shell Terminal in eclipse, you will meet the > error"Error connecting localhost:8101 : SSH client error: verify: false". > Please refer karaf jira KARAF-1513 for the root cause. > https://issues.apache.org/jira/browse/KARAF-1513 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707023#comment-13707023 ] Jarek Gawor commented on GERONIMO-6481: --- A few comments: 1) The latest released version of Karaf 2.2.x is 2.2.11. It would be preferable to upgrade to the latest 2.2.x version unless of course this a huge hassle. 2) The eclipse project files are not under source control for the Geronimo server project. The only project that I'm aware of that has them under source control is the Geronimo Eclipse Plugin project. So, I don't think you need to worry about this. 3) Make sure to double check that any shared third party dependencies between Karaf and Geronimo are (more or less) on the same level. However, there are a few old dependencies that we might keep as it (for example aries blueprint). > Karaf shell ssh bundle for IBM JDK SR10 host key issue > -- > > Key: GERONIMO-6481 > URL: https://issues.apache.org/jira/browse/GERONIMO-6481 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0.0, 3.0.1 >Reporter: xiezhi >Assignee: Andy McCright > Attachments: 6481-patch.txt > > > When you launch Geronimo Shell Terminal in eclipse, you will meet the > error"Error connecting localhost:8101 : SSH client error: verify: false". > Please refer karaf jira KARAF-1513 for the root cause. > https://issues.apache.org/jira/browse/KARAF-1513 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6482) Ensure loading of JVM ext classloader classes from Geronimo bundles
[
https://issues.apache.org/jira/browse/GERONIMO-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707005#comment-13707005
]
Jarek Gawor commented on GERONIMO-6482:
---
I realized that Karaf sets this property in the etc/config.properties file so I
moved your change to that file as well in Geronimo to make things consistent.
The end result is pretty much the same anyway. Changes committed in revision
1502585 in 3.0 branch. Please double check if things are still working ok and
if so close the bug.
Thanks for the patch!
> Ensure loading of JVM ext classloader classes from Geronimo bundles
> ---
>
> Key: GERONIMO-6482
> URL: https://issues.apache.org/jira/browse/GERONIMO-6482
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: osgi
>Affects Versions: 3.0.1
>Reporter: Andy McCright
>Assignee: Andy McCright
>Priority: Minor
> Attachments: sys-prop-patch.txt
>
>
> IBM has changed the classloader used to load com.sun.* (specifically
> com.sun.script.javascript) classes in JDK 7. In JDK 6, these classes were
> loaded by the JVM's boot classloader - in JDK 7, they are loaded via the
> JVM's ext classloader (a child classloader of the boot loader). This change
> has the effect of breaking servlet code like this:
> ScriptEngineManager manager = new ScriptEngineManager();
> ScriptEngine engine = manager.getEngineByName("JavaScript");
> if(engine == null) {
> throw new RuntimeException("Oh no, unable to find a script engine
> found for JavaScript");
> }
> When running Geronimo 3.0.1 on JDK 6, this code works (engine is non-null, no
> exception is thrown). When I switch to JDK7, I see:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> java.lang.RuntimeException: Oh no, unable to find a script engine found for
> JavaScript
> at org.apache.jsp.HelloWorld_jsp._jspService(HelloWorld_jsp.java:96)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:731)
> at
> org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48)
> at
> org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
> at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:267)
> at
> org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:397)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
> at java.lang.Thread.run(Thread.java:769)
> The reason this fails is that the bundle's clas
[jira] [Commented] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703351#comment-13703351 ] Jarek Gawor commented on GERONIMO-6481: --- Hopefully, since this looks like it is fixed in Karaf 2.2.8 we can just upgrade Geronimo to use Karaf 2.2.8 or so? > Karaf shell ssh bundle for IBM JDK SR10 host key issue > -- > > Key: GERONIMO-6481 > URL: https://issues.apache.org/jira/browse/GERONIMO-6481 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 3.0.0, 3.0.1 >Reporter: xiezhi > > When you launch Geronimo Shell Terminal in eclipse, you will meet the > error"Error connecting localhost:8101 : SSH client error: verify: false". > Please refer karaf jira KARAF-1513 for the root cause. > https://issues.apache.org/jira/browse/KARAF-1513 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: JDK 7 Classloading Behavior Change
Does this work ok if the "org.osgi.framework.bundle.parent" property
is set to "framework"? I would think so but would like to get
confirmation. This property is set to "framework" in Karaf so I would
prefer to go with that. If the property is not set, it defaults to
"boot" (the boot classloader) which kind of explains the problem.
Jarek
On Wed, Jul 3, 2013 at 12:38 PM, Andy McCright
wrote:
> Hi All,
>
> I have noticed that IBM has changed the classloader used to load com.sun.*
> (specifically com.sun.script.javascript) classes in JDK 7. In JDK 6, these
> classes were loaded by the JVM's boot classloader - in JDK 7, they are
> loaded via the JVM's ext classloader (a child classloader of the boot
> loader). This change has the effect of breaking servlet code like this:
>
>
> ScriptEngineManager manager = new ScriptEngineManager();
> ScriptEngine engine = manager.getEngineByName("JavaScript");
> if(engine == null) {
> throw new RuntimeException("Oh no, unable to find a script engine
> found for JavaScript");
> }
>
> When running Geronimo 3.0.1 on JDK 6, this code works (engine is non-null,
> no exception is thrown). When I switch to JDK7, I see:
> ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
> Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
> java.lang.RuntimeException: Oh no, unable to find a script engine found for
> JavaScript
> at org.apache.jsp.HelloWorld_jsp._jspService(HelloWorld_jsp.java:96)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
> at
> org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:731)
> at
> org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48)
> at
> org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009)
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
> at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:267)
> at
> org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:397)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
> at java.lang.Thread.run(Thread.java:769)
>
> The reason this fails is that the bundle's classloader's parent loader is
> the JVM's boot classloader, not the ext loader - so it cannot load the
> com.sun.* classes that it needs (and that it could in JDK6).
>
> One solution to this is to add the following line to
> /etc/system.properties:
> osgi.parentClassloader=ext
>
> This forces the bundle's to search the ext loader (in addition to the boot
> loader) on boot delegated loads.
>
> I'm wondering if there should be a more permanent fix... here are a few
> suggestions:
> 1) Work with the JDK teams to revert back to the old behavior - I have a
> ticket open with JDK support, but they apparently moved the com.sun.*
> classes to the ext loader for a security issue, so it may be a hard sell to
> get them to move it back.
> 2) Update the default system.properties to include
> osgi.parentClassloader=ext
> 3) Modify the ClassLoaderHook's getBundleClassLoaderParent() method to
> return the ext loader ( ClassLoader.getSystemClassLoader().getParent() ).
>
> If #1 is not an option, then I think I like optino #2 better than #3, as it
> allows users to change it easily if
Re: IMPORTANT: Major Confluence Upgrade Coming Soon. Please review test instance now.
I just re-enabled our website publication and forced all confluence pages to be regenerated. You might see a lot of commits from the website buildbot soon. Thanks to Dan Kulp's work the update wasn't too bad for us. Of course, if you see something wrong on the website let us know. We are now also pulling the Confluence exporter code directly from CXF (instead of maintaining our own version). That should make things easier to deal with in the future. Thanks, Jarek On Thu, Jun 20, 2013 at 3:50 PM, Jarek Gawor wrote: > Hi all, > > I disabled our cwiki site publication because of the pending cwiki > upgrade. I think we will have some work to do again to make sure the > Geronimo web pages are exported correctly. Dan Kulp already dealt with > some of this and hopefully things will be easier for us > (http://camel.465427.n5.nabble.com/Web-site-more-or-less-ready-for-new-confluence-td5734450.html). > I won't be able to work on this anytime soon (out on vacation next > week) but maybe somebody else can pick this up soon. > > Jarek > > -- Forwarded message -- > From: gmcdonald > Date: Tue, Jun 18, 2013 at 7:56 AM > Subject: IMPORTANT: Major Confluence Upgrade Coming Soon. Please > review test instance now. > To: p...@apache.org, gene...@incubator.apache.org > > > [PMCs please forward to your dev list ; Incubator Mentors please forward to > your Podling dev list. > Note that this message may be received twice as it will also go to > committers@ list.] > > > Hi All, > > If your project has a Confluence Wiki then this is an IMPORTANT announcement > for you and your project. Please read this email carefully. > > NOTICE: The ASF Confluence instance is planned to be upgraded this Saturday > 22nd June 2013. Judging by the time taken to upgrade the test instance, > please expect the service to be in a down or read only state for the entire > day. > > This email is to let you know that a test upgrade has already occurred and > is live for you to play with now. This gives us all an opportunity to test > for stability as well as any upgrade/plugin issues that might have happened > along the way. > > Our current confluence wiki is at version 3.4.9 from way back in February > 2011 and Atlassian have released a further 45 updates along the way, > including another 2 major versions. > The test instance has been upgraded several times along the way, with > database surgery, operating system and server changes along the way. > > There have been casualties. Most notably is the Autoexport Plugin has had to > be disabled permanently as during extensive testing, this plugin stopped > working on version 4.3. Templates and Macros are also affected with major > changes from wiki markup to xhtml amongst other things. Some plugins > survived with upgrades all the way whilst some have been > decommissioned/replaced or have changed to 'paid for' versions that we need > to sort out licensing for. Nothing major that I can tell, but that's where > you lot come in with your testing of your own spaces. > > Please familiarise yourself with what's new in Confluence 5.1 at > https://confluence.atlassian.com/display/DOC/Confluence+5.1+Release+Notes > and also take a good look around our upgraded test instance. Do not worry > about mucking anything up on the test instance as that is what it is there > for. Any changes/additions made will be lost on Saturday when a new > migration will take place. The current confluence version will remain online > in a read only state until the new version is completed. > > A jira ticket has been raised at > https://issues.apache.org/jira/browse/INFRA-6406 where projects can add > comments on any issues they are having with the test instance as compared to > their old site. Just problems only please, do not turn it into a how to use > confluence 5 thread. In addition, if there are any features that you > currently use that do not work in the test instance, please replicate the > feature in the current production TEST space so that I can test them all in > the one place along the way. (Ask if you need create page permissions to > cwiki.apache.org/confluence/display/TEST ) > > It may be possible in the future to replace Autoexport by playing around > with the API to export the pages but this is not a priority, nor is it > supported. We warned projects long ago that the Autoexport Tool would be > incompatible with future Confluence versions and that time has now come. > > Ok so, please test and report to the Jira Issue mentioned anything amiss > with your space. Go to https://cwiki2.apache.org/confluence and have a play > around. You have 3 DAYS to report anything you find. > > Thanks > > Gavin (ASF Infra) > > > > - > To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org > For additional commands, e-mail: private-h...@incubator.apache.org
[jira] [Commented] (GERONIMO-6477) Misconfigured RMI classloader
[ https://issues.apache.org/jira/browse/GERONIMO-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696905#comment-13696905 ] Jarek Gawor commented on GERONIMO-6477: --- Remote exploits can be prevented by hiding the naming (1099) and JMX () ports behind a firewall or binding the ports to a local network interface. Fix for this issue was committed in revision 1458113. > Misconfigured RMI classloader > - > > Key: GERONIMO-6477 > URL: https://issues.apache.org/jira/browse/GERONIMO-6477 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker > to send a serialized object via JMX that could compromise the system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6477) Misconfigured RMI classloader
[ https://issues.apache.org/jira/browse/GERONIMO-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6477. --- Resolution: Fixed CVE-2013-1777 was assigned for this issue. The original issue was discovered by Pierre Ernst of IBM Canada Ltd. > Misconfigured RMI classloader > - > > Key: GERONIMO-6477 > URL: https://issues.apache.org/jira/browse/GERONIMO-6477 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker > to send a serialized object via JMX that could compromise the system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6477) Misconfigured RMI classloader
Jarek Gawor created GERONIMO-6477: - Summary: Misconfigured RMI classloader Key: GERONIMO-6477 URL: https://issues.apache.org/jira/browse/GERONIMO-6477 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: core Affects Versions: 3.0-beta-1, 3.0.0, 3.0-M1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker to send a serialized object via JMX that could compromise the system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[SECURITY] CVE-2013-1777: Apache Geronimo 3 RMI classloader exposure
CVE-2013-1777: Apache Geronimo 3 RMI classloader exposure Severity: Important Vendor: The Apache Software Foundation Version Affected: Apache Geronimo 3.0 Apache Geronimo 3.0 Beta 1 Apache Geronimo 3.0 M1 Description: A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker to send a serialized object via JMX that could compromise the system. Mitigation: Geronimo 3.0, Beta 1 or M1 users are strongly encouraged to upgrade to Geronimo 3.0.1. Remote exploits can be prevented by hiding the naming (1099) and JMX () ports behind a firewall or binding the ports to a local network interface. Credit: This issue was discovered by Pierre Ernst of IBM Canada Ltd. References: http://geronimo.apache.org/security-reports.html
[jira] [Commented] (GERONIMO-6472) SpnegoLoginModule problems
[ https://issues.apache.org/jira/browse/GERONIMO-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689922#comment-13689922 ] Jarek Gawor commented on GERONIMO-6472: --- Committed fixes to 3.0 branch (revision 1495244), 2.2 branch (revision 1495259) and 2.1 branch (revision 1495258). > SpnegoLoginModule problems > -- > > Key: GERONIMO-6472 > URL: https://issues.apache.org/jira/browse/GERONIMO-6472 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.1.8 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > A few different problems were discovered with the SpnegoLoginModule: > 1) The searchFilter to lookup the user information uses cn attribute for > matching. The cn (common name) might be different that the actual account > name, and so the user lookup might fail. > 2) NPE when memberOf attribute is not there > 3) ArrayOutOfBoundsException when parsing group names -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6472) SpnegoLoginModule problems
Jarek Gawor created GERONIMO-6472: - Summary: SpnegoLoginModule problems Key: GERONIMO-6472 URL: https://issues.apache.org/jira/browse/GERONIMO-6472 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1.8 Reporter: Jarek Gawor Assignee: Jarek Gawor A few different problems were discovered with the SpnegoLoginModule: 1) The searchFilter to lookup the user information uses cn attribute for matching. The cn (common name) might be different that the actual account name, and so the user lookup might fail. 2) NPE when memberOf attribute is not there 3) ArrayOutOfBoundsException when parsing group names -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Fwd: IMPORTANT: Major Confluence Upgrade Coming Soon. Please review test instance now.
Hi all, I disabled our cwiki site publication because of the pending cwiki upgrade. I think we will have some work to do again to make sure the Geronimo web pages are exported correctly. Dan Kulp already dealt with some of this and hopefully things will be easier for us (http://camel.465427.n5.nabble.com/Web-site-more-or-less-ready-for-new-confluence-td5734450.html). I won't be able to work on this anytime soon (out on vacation next week) but maybe somebody else can pick this up soon. Jarek -- Forwarded message -- From: gmcdonald Date: Tue, Jun 18, 2013 at 7:56 AM Subject: IMPORTANT: Major Confluence Upgrade Coming Soon. Please review test instance now. To: p...@apache.org, gene...@incubator.apache.org [PMCs please forward to your dev list ; Incubator Mentors please forward to your Podling dev list. Note that this message may be received twice as it will also go to committers@ list.] Hi All, If your project has a Confluence Wiki then this is an IMPORTANT announcement for you and your project. Please read this email carefully. NOTICE: The ASF Confluence instance is planned to be upgraded this Saturday 22nd June 2013. Judging by the time taken to upgrade the test instance, please expect the service to be in a down or read only state for the entire day. This email is to let you know that a test upgrade has already occurred and is live for you to play with now. This gives us all an opportunity to test for stability as well as any upgrade/plugin issues that might have happened along the way. Our current confluence wiki is at version 3.4.9 from way back in February 2011 and Atlassian have released a further 45 updates along the way, including another 2 major versions. The test instance has been upgraded several times along the way, with database surgery, operating system and server changes along the way. There have been casualties. Most notably is the Autoexport Plugin has had to be disabled permanently as during extensive testing, this plugin stopped working on version 4.3. Templates and Macros are also affected with major changes from wiki markup to xhtml amongst other things. Some plugins survived with upgrades all the way whilst some have been decommissioned/replaced or have changed to 'paid for' versions that we need to sort out licensing for. Nothing major that I can tell, but that's where you lot come in with your testing of your own spaces. Please familiarise yourself with what's new in Confluence 5.1 at https://confluence.atlassian.com/display/DOC/Confluence+5.1+Release+Notes and also take a good look around our upgraded test instance. Do not worry about mucking anything up on the test instance as that is what it is there for. Any changes/additions made will be lost on Saturday when a new migration will take place. The current confluence version will remain online in a read only state until the new version is completed. A jira ticket has been raised at https://issues.apache.org/jira/browse/INFRA-6406 where projects can add comments on any issues they are having with the test instance as compared to their old site. Just problems only please, do not turn it into a how to use confluence 5 thread. In addition, if there are any features that you currently use that do not work in the test instance, please replicate the feature in the current production TEST space so that I can test them all in the one place along the way. (Ask if you need create page permissions to cwiki.apache.org/confluence/display/TEST ) It may be possible in the future to replace Autoexport by playing around with the API to export the pages but this is not a priority, nor is it supported. We warned projects long ago that the Autoexport Tool would be incompatible with future Confluence versions and that time has now come. Ok so, please test and report to the Jira Issue mentioned anything amiss with your space. Go to https://cwiki2.apache.org/confluence and have a play around. You have 3 DAYS to report anything you find. Thanks Gavin (ASF Infra) - To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org For additional commands, e-mail: private-h...@incubator.apache.org
Fwd: [SECURITY] Frame injection vulnerability in published Javadoc
I used the tool to fix up all Geronimo javadoc pages - see revision 866646. Jarek -- Forwarded message -- From: Mark Thomas Date: Thu, Jun 20, 2013 at 4:29 AM Subject: [SECURITY] Frame injection vulnerability in published Javadoc To: committ...@apache.org Cc: r...@apache.org Hi All, Oracle has announced [1], [2] a frame injection vulnerability in Javadoc generated by Java 5, Java 6 and Java 7 before update 22. The infrastructure team has completed a scan of our current project websites and identified over 6000 instances of vulnerable Javadoc distributed across most TLPs. The chances are the project(s) you contribute to is(are) affected. A list of projects and the number of affected Javadoc instances per project is provided at the end of this e-mail. Please take the necessary steps to fix any currently published Javadoc and to ensure that any future Javadoc published by your project does not contain the vulnerability. The announcement by Oracle includes a link to a tool that can be used to fix Javadoc without regeneration. The infrastructure team is investigating options for preventing the publication of vulnerable Javadoc. The issue is public and may be discussed freely on your project's dev list. Thanks, Mark (ASF Infra) [1] http://www.oracle.com/technetwork/topics/security/javacpujun2013-1899847.html [2] http://www.kb.cert.org/vuls/id/225657 Project Instances abdera.apache.org 1 accumulo.apache.org 2 activemq.apache.org 105 any23.apache.org13 archiva.apache.org 4 archive.apache.org 13 aries.apache.org7 avro.apache.org 23 axis.apache.org 5 beehive.apache.org 16 bval.apache.org 12 camel.apache.org786 cayenne.apache.org 4 chemistry.apache.org6 click.apache.org3 cocoon.apache.org 6 commons.apache.org 34 continuum.apache.org9 creadur.apache.org 19 crunch.apache.org 4 ctakes.apache.org 2 curator.apache.org 4 cxf.apache.org 6 db.apache.org 39 directory.apache.org4 empire-db.apache.org1 felix.apache.org5 flume.apache.org5 geronimo.apache.org 241 giraph.apache.org 6 gora.apache.org 3 hadoop.apache.org 21 hbase.apache.org2 hive.apache.org 4 hivemind.apache.org 10 incubator.apache.org355 jackrabbit.apache.org 9 jakarta.apache.org 39 james.apache.org53 jena.apache.org 5 juddi.apache.org3 lenya.apache.org46 logging.apache.org 111 lucene.apache.org 713 manifoldcf.apache.org 112 marmotta.apache.org 1 maven.apache.org1623 maventest.apache.org1178 mina.apache.org 2 mrunit.apache.org 3 myfaces.apache.org 348 nutch.apache.org8 oltu.apache.org 11 oodt.apache.org 1 ooo-site.apache.org 1 oozie.apache.org10 openjpa.apache.org 20 opennlp.apache.org 9 pdfbox.apache.org 1 pig.apache.org 7 pivot.apache.org1 poi.apache.org 1 portals.apache.org 35 river.apache.org2 santuario.apache.org1 shale.apache.org55 shiro.apache.org3 sling.apache.org2 sqoop.apache.org4 struts.apache.org 190 subversion.apache.org 3 synapse.apache.org 1 syncope.apache.org 2 tapestry.apache.org 6 tika.apache.org 9 tiles.apache.org12 turbine.apache.org 100 tuscany.apache.org 4 uima.apache.org 12 velocity.apache.org 41 whirr.apache.org2 wicket.apache.org 3 wink.apache.org 13 ws.apache.org 22 xalan.apache.org1 xerces.apache.org 5 xml.apache.org 1 xmlbeans.apache.org 3 zookeeper.apache.org18
[jira] [Commented] (GERONIMO-6462) API jar for JSR 356 - WebSockets 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680934#comment-13680934 ] Jarek Gawor commented on GERONIMO-6462: --- Committed your patch in revision 1492048. Thanks! Snapshot published at: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-websockets_1.0_spec/1.0-SNAPSHOT/ > API jar for JSR 356 - WebSockets 1.0 > > > Key: GERONIMO-6462 > URL: https://issues.apache.org/jira/browse/GERONIMO-6462 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter >Assignee: Andy McCright > Attachments: websockets-patch.txt > > > New jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Java 7 genesis and specs
Hi all, Some of the new Java EE 7 spec API (as for example servlet 3.1) requires Java 7 to build. For that I created genesis-java7-flava in genesis with Java 7 settings and updated the specs module to compile with Java 7. Buildbot was updated as well to use Java 7 for the genesis and specs modules. Even though Java 7 is used to compile some of the older spec jars, the compiler is configured with the right -source/-target options so that everything should be still fine on the older JVMs. Let me know if there are any concerns with this, Jarek
[jira] [Commented] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679667#comment-13679667 ] Jarek Gawor commented on GERONIMO-6453: --- Btw, for now I manually published a snapshot of the spec jar: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-servlet_3.1_spec/1.0-SNAPSHOT/ > API jar for JSR 340 - Servlet 3.1 > - > > Key: GERONIMO-6453 > URL: https://issues.apache.org/jira/browse/GERONIMO-6453 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter >Assignee: Andy McCright > Attachments: patch.txt > > > Update jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Would like to contribute
Andy, I think you should be in the contributors group now. Please see if assigning JIRA works for you now. Jarek On Mon, Jun 10, 2013 at 10:44 AM, Andrew McCright wrote: > Thanks for the clarification - my ID is: andymc > >Jira > > > From:Jean-Louis MONTEIRO > To:dev@geronimo.apache.org, > Date:06/10/2013 09:43 AM > Subject:Re: Would like to contribute > > > > > Hi, > > Kevan was asking your JIRA ID to assign you to those JIRAs. > The JIRA ID is the one you use to connect to issues.a.o > > Thanks, > Jean-Louis > > > 2013/6/10 Andrew McCright > Hi Kevan, > > Thanks! The JIRA IDs that I am interested in are: > > 6450 - Concurrency Utils > 6452 - JAX-RS 2.0 > 6453 - Servlet 3.1 APIs - I've submitted a patch for this one. > 6461 - JSON-P > 6462 - WebSockets > > Can you add me to the contributor list? At that point should I be able to > assign JIRAs to myself, or will I need a committer to assign them to me? > > Thanks again, > > Andy > > > > > > From:Kevan Miller > To:dev@geronimo.apache.org, > Date:06/09/2013 05:35 AM > Subject:Re: Would like to contribute > > > > > > > On Jun 7, 2013, at 3:16 PM, Deepal Jayasinghe wrote: > >> A JIRA cannot be assigned to you unless you are a developer (committer), >> but you should be able to contribute to the issue such as submit patches >> etc… > > Not quite. There is a JIRA category of 'contributor'. We allow JIRA's to be > assigned to Geronimo contributors. You are correct that anyone can submit > patches. > > --kevan > > > > > -- > Jean-Louis
[jira] [Commented] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679547#comment-13679547 ] Jarek Gawor commented on GERONIMO-6453: --- I had a little bit of problems applying your patch but eventually managed to resolve the issues. Your patch was applied in revision 1491469. The servlet 3.1 API require Java 7 to compile. Currently, the entire spec project is setup to be compiled with Java 6 so that's something we still need to figure out. > API jar for JSR 340 - Servlet 3.1 > - > > Key: GERONIMO-6453 > URL: https://issues.apache.org/jira/browse/GERONIMO-6453 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: patch.txt > > > Update jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: enabled RAT checks during build
Running findbugs for example on each build makes sense to me at dev time. Running rat doesn't because most of the time one is changing an existing file and not adding new ones. Running rat at release time (as the name of the tool suggests) or deploy time make sense to me as that's when we want to make sure everything is in proper shape. So, my preference as mentioned before is to run it in the deploy phase as it still will catch the problems early but won't fail builds for silly reasons. Jarek On Wed, May 29, 2013 at 11:19 AM, Romain Manni-Bucau wrote: > Hi > > i like to get it by default, > > @Jarek: rat can be skipped with a system property, isn't it enough for dev > time? > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/5/29 Jarek Gawor >> >> I don't know about others but my source tree is usually polluted with >> patch files and other files that I create during >> development/testing/debugging. With Rat enabled by default my build >> will fail (as it does currently after doing svn up on xbean). So I >> would prefer to either delay RAT until the deploy phase or just enable >> RAT on the buildbot setup for xbean. >> >> Jarek >> >> >> On Wed, May 29, 2013 at 5:01 AM, Mark Struberg wrote: >> > hi folks! >> > >> > I've enabled apache-rat in the whole xbean build. Which means the build >> > is now defunct due to a few missing licenses. >> > Hope we gonna fix those soon... >> > >> > LieGrue, >> > strub > >
Re: [VOTE] take2 - release xbean-3.14
+1
Jarek
On Thu, May 30, 2013 at 3:03 AM, Mark Struberg wrote:
>
> Hi!
>
> I'd like to call a 2nd VOTE for releasing xbean-3.14.
> This time I fixed the missing license headers and activated RAT for each
> build.
>
>
> The staging repo can be found here:
> https://repository.apache.org/content/repositories/orgapachegeronimo-038/
>
> The tag is https://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.14/
>
> And here comes the source.zip:
>
> https://repository.apache.org/content/repositories/orgapachegeronimo-038/org/apache/xbean/xbean/3.14/xbean-3.14-source-release.zip
>
> sha1:
>
>
> 0362adbf3364a86c5fa91001a72152a2a3a83935
>
> The VOTE is open for 72h
>
> [+1] all fine, let's ship it
> [+0] meh don't care
> [-1] nope because it contains a ${blocker}
>
>
> LieGrue,
> strub
>
Re: [VOTE] Release Geronimo eclipse plugin 3.0.1 - second try
+1. Looks good to me. RAT complains about 2 files plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd and plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd but we can ignore those. Thanks again for putting this together! Jarek On Wed, May 29, 2013 at 4:31 AM, Forrest Xia wrote: > Hi Devs, > > Second try to release GEP 3.0.1. It fixed the build problem on Mac OS. > > Please vote Geronimo eclipse plugin(GEP) 3.0.1 release. This is a release > along with Geronimo server runtime release 3.0.1. > > For details, see > http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.1.txt > > The GEP code up for vote is: > https://repository.apache.org/content/repositories/orgapachegeronimo-031/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-031/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.1/geronimo-eclipse-plugin-3.0.1-source-release.zip > > To build this source code, you need to build maven-eclipsepde-plugin 1.2 > first(Its vote is ongoing now): > http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/maven-plugins-1.2/ > > NOTE: Please use Maven 2.2.1 and Java 6 to build them. > > The GEP staging update site is: > http://people.apache.org/builds/geronimo/eclipse/updates/ > > The release staging site is: > https://repository.apache.org/content/repositories/orgapachegeronimo-031 > > The tag has created at: > http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.1/ > > Vote will be at most open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Thanks! > > Regards, Forrest
Re: [VOTE] Geronimo devtools maven-eclipsepde-plugin 1.2 release
+1 Looks good to me. Thank you! Jarek On Wed, May 29, 2013 at 2:46 AM, Forrest Xia wrote: > Hi all, > > To make Geronimo eclipse plugin compiled on Mac OS, we need to release a new > maven-eclipsepde-plugin 1.2. > > Here are artifacts for vote: > Source code: > https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.2/maven-eclipsepde-plugin-1.2-sources.jar > > svn tag: > http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/maven-plugins-1.2/ > > NOTE: please build it with maven 2.2.1 and Java 6. > > Vote will be at most open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > -- > Thanks! > > Regards, Forrest
Re: enabled RAT checks during build
I don't know about others but my source tree is usually polluted with patch files and other files that I create during development/testing/debugging. With Rat enabled by default my build will fail (as it does currently after doing svn up on xbean). So I would prefer to either delay RAT until the deploy phase or just enable RAT on the buildbot setup for xbean. Jarek On Wed, May 29, 2013 at 5:01 AM, Mark Struberg wrote: > hi folks! > > I've enabled apache-rat in the whole xbean build. Which means the build is > now defunct due to a few missing licenses. > Hope we gonna fix those soon... > > LieGrue, > strub
Re: [DISCUSSION] How to compile GEP
Alan, Kevan, can you try changing the maven-eclipsepde-plugin version dependency to 1.2-SNAPSHOT and see if the code at least compiles now? If that works, then I think we should release the 1.2 version of maven-eclipsepde-plugin and update GEP to use it. Jarek On Tue, May 28, 2013 at 11:32 AM, Alan Cabrera wrote: > > On May 28, 2013, at 8:14 AM, Kevan Miller wrote: > >> >> On May 28, 2013, at 11:05 AM, Forrest Xia wrote: >> >>> What's your configuration on Mac OS? >>> >>> Java version? In what module does the problem happen? >> >> I've tried both Java 6 and Java 7. >> >> Java 6 fails with: >> >> >> [INFO] >> >> [ERROR] FATAL ERROR >> [INFO] >> >> [INFO] An invalid artifact was detected. >> >> This artifact might be in your project's POM, or it might have been included >> transitively during the resolution process. Here is the information we do >> have for this artifact: >> >>o GroupID: org.eclipse.plugins >>o ArtifactID: org.eclipse.swt.cocoa.macosx >>o Version: <<< MISSING >>> >>o Type:jar >> > > I get the same error, Java 6. > > > Regards, > Alan > >
Re: Is there a need to release GEP 3.0.1 for Geronimo 3.0.1?
I'm not entirely sure. Things just got mixed up I guess. I was actually thinking about moving sever/3.0 branch into trunk and moving existing server/trunk into some experimental branch. Jarek On Fri, May 24, 2013 at 11:48 AM, Forrest Xia wrote: > Just curious, Is there any reason made changes to trunk, but not 3.0 > branches of GEP? > > I thought we should follow this convention: GEP trunk supports server trunk, > GEP 3.0 branch supports server 3.0. branch. > > > On Fri, May 24, 2013 at 11:28 PM, Jarek Gawor wrote: >> >> I think you used a wrong branch to compare. The latest updates went >> into devtools/eclipse-plugin/trunk and not >> devtools/eclipse-plugin/branches/3.0. There was a definitely lots of >> changes since 3.0.0 so yes I would vote to release it. >> >> Jarek >> >> On Fri, May 24, 2013 at 2:01 AM, Forrest Xia wrote: >> > Hi all, >> > >> > I checked GEP 3.0 branch revision history, but not found any new code >> > fixes >> > after its 3.0.0 release back to July of 2012, so my question is, is >> > there a >> > need to make a new GEP release for 3.0.1 server? >> > >> > I did some simple testing, the current GEP 3.0.0 release works well with >> > 3.0.1 server. >> > >> > -- >> > Thanks! >> > >> > Regards, Forrest > > > > > -- > Thanks! > > Regards, Forrest
Re: Is there a need to release GEP 3.0.1 for Geronimo 3.0.1?
I think you used a wrong branch to compare. The latest updates went into devtools/eclipse-plugin/trunk and not devtools/eclipse-plugin/branches/3.0. There was a definitely lots of changes since 3.0.0 so yes I would vote to release it. Jarek On Fri, May 24, 2013 at 2:01 AM, Forrest Xia wrote: > Hi all, > > I checked GEP 3.0 branch revision history, but not found any new code fixes > after its 3.0.0 release back to July of 2012, so my question is, is there a > need to make a new GEP release for 3.0.1 server? > > I did some simple testing, the current GEP 3.0.0 release works well with > 3.0.1 server. > > -- > Thanks! > > Regards, Forrest
Re: [VOTE] Release Geronimo 3.0.1 - third try
Things look pretty good to me +1. Thanks! Jarek On Thu, May 23, 2013 at 1:26 AM, Forrest Xia wrote: > This is the third time to vote for Geronimo 3.0.1 release. Thanks Jarek to > help on fixing Geronimo-6034. > > For Geronimo 3.0.1 release, there are these major changes: > 1. JSF 2.1 support > 2. JDBC 4 support > 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ > 4. Quite a few bugs fixes > > For details, see > http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt > > The server code up for vote is: > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip > > The binary code up for vote is: > Java EE 6 Full Profile Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip > > Java EE 6 Web Profile Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip > > Little-G Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-034/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip > > Staging repo is: > https://repository.apache.org/content/repositories/orgapachegeronimo-034/ > > The tag has created at: > http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1 > > Java EE 6 TCKs all passed! > > Vote will be at least open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Thanks! > > Regards, Forrest
[jira] [Resolved] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6451. --- Resolution: Fixed Resolving as most of the API is defined now. Please open another bug / task for fixing any potential problems discovered by TCK testing. > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, > jpa2.1-src.patch.txt > > > Updated JPA 2.1 jar for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6034) testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664288#comment-13664288 ] Jarek Gawor commented on GERONIMO-6034: --- Looks like the problem here is that our porting code - specifically BeansImpl.isProxy() hasn't been updated to deal with changing package names of dynamic proxies. Here are the package names I see for a few different maintenance releases of Oracle Java 6: jdk6_43: class com.sun.proxy.$Proxy0 jdk6_39: class sun.proxy.$Proxy0 jdk6_23: class $Proxy0 Anyway, I updated the code in revision 1485297 and the tests appears to be passing now. > testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest) > - > > Key: GERONIMO-6034 > URL: https://issues.apache.org/jira/browse/GERONIMO-6034 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: David Blevins > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Geronimo 3.0.1 - second try
Sorry, I still see 3.0.1-SNAPSHOT in ./plugins/console/console-tomcat-server/pom.xml ./plugins/console/console-jetty-server/pom.xml Jarek On Tue, May 21, 2013 at 9:57 AM, Forrest Xia wrote: > +1 myself > > > On Tue, May 21, 2013 at 3:35 PM, Forrest Xia wrote: >> >> Hi Devs, >> >> Please vote Geronimo 3.0.1 release with these major differences from the >> previous release: >> 1. JSF 2.1 support >> 2. JDBC 4 support >> 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ >> 4. Quite a few bugs fixes >> >> For details, see >> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt >> >> The server code up for vote is: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip >> >> The binary code up for vote is: >> Java EE 6 Full Profile Tomcat Assemblies: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip >> >> Java EE 6 Web Profile Tomcat Assemblies: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip >> >> Little-G Tomcat Assemblies: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip >> >> Staging repo is: >> https://repository.apache.org/content/repositories/orgapachegeronimo-019/ >> >> The tag has created at: >> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1 >> >> Java EE 6 TCKs all passed! >> >> Vote will be at least open for 72 hours. >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> -- >> Thanks! >> >> Regards, Forrest > > > > > -- > Thanks! > > Regards, Forrest
Re: [DISCUSS] Release Geronimo 3.0.1
Yes, that's bad. Looks like maven release plugin was executed with -Pnoclustering option. Which means that the plugin won't process certain modules (update the version in poms) but since the plugin creates a tag from the branch, all source code will be included. So if you build from tag (or source zip or tar.gz) you might end up compiling code that was skipped by the release plugin. So, I guess if there is something we don't want to include in a release, we shouldn't rely on a profile option during a release but instead either 1) svn delete the modules we don't want before the release or 2) update poms appropriately so that modules we don't want aren't compiled by default before the release. Or any other better ideas? Jarek On Mon, May 20, 2013 at 8:25 AM, Kevan Miller wrote: > > I've been trying off and on to get a clean build since Friday. I'm currently > failing with: > > [ERROR] Failed to execute goal on project geronimo-clustering-wadi: Could not > resolve dependencies for project > org.apache.geronimo.modules:geronimo-clustering-wadi:bundle:3.0.1-SNAPSHOT: > Could not find artifact > org.apache.geronimo.ext.tomcat:tribes:jar:7.0.39.1-SNAPSHOT in > apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1] > > I can try to clean out my maven repo. See if that helps. However: > > looks like a lot of pom.xml files have 's pointing to 3.0.1-SNAPSHOT. > Try running 'grep -Rni --include=pom.xml snapshot *' > > --kevan > > On May 17, 2013, at 9:56 AM, Forrest Xia wrote: > >> Hi Devs, >> >> Please vote Geronimo 3.0.1 release with these major differences from the >> previous release: >> 1. JSF 2.1 support >> 2. JDBC 4 support >> 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ >> 4. Quite a few bugs fixes >> >> For details, see >> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt >> >> The server code up for vote is: >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip >> >> The binary code up for vote is: >> Java EE 6 Full Profile Tomcat Assemblies: >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip >> >> Java EE 6 Web Profile Tomcat Assemblies: >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip >> >> Little-G Tomcat Assemblies: >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip >> >> Staging repo is: >> https://repository.apache.org/content/repositories/orgapachegeronimo-009/ >> >> The tag has created at: >> http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1 >> >> Java EE 6 TCKs all passed! >> >> Vote will be at least open for 72 hours. >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> -- >> Thanks! >> >> Regards, Forrest >
Re: [VOTE] Release Geronimo 3.0.1
-1 based on the issue that Kevan found. Jarek On Fri, May 17, 2013 at 9:56 AM, Forrest Xia wrote: > Hi Devs, > > Please vote Geronimo 3.0.1 release with these major differences from the > previous release: > 1. JSF 2.1 support > 2. JDBC 4 support > 3. Some components upgrade, including Tomcat, JPA, Yoko, Tranql, ActiveMQ > 4. Quite a few bugs fixes > > For details, see > http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1/RELEASE_NOTES-3.0.1.txt > > The server code up for vote is: > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/geronimo/3.0.1/geronimo-3.0.1-source-release.zip > > The binary code up for vote is: > Java EE 6 Full Profile Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0.1/geronimo-tomcat7-javaee6-3.0.1-bin.zip > > Java EE 6 Web Profile Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6-web/3.0.1/geronimo-tomcat7-javaee6-web-3.0.1-bin.zip > > Little-G Tomcat Assemblies: > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.tar.gz > https://repository.apache.org/content/repositories/orgapachegeronimo-009/org/apache/geronimo/assemblies/geronimo-tomcat7-minimal/3.0.1/geronimo-tomcat7-minimal-3.0.1-bin.zip > > Staging repo is: > https://repository.apache.org/content/repositories/orgapachegeronimo-009/ > > The tag has created at: > http://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-3.0.1 > > Java EE 6 TCKs all passed! > > Vote will be at least open for 72 hours. > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Thanks! > > Regards, Forrest
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661000#comment-13661000 ] Jarek Gawor commented on GERONIMO-6451: --- Committed your patch in revision 1483970. Thanks! Are you planning to validate this against TCK (signature tests)? > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, > jpa2.1-src.patch.txt > > > Updated JPA 2.1 jar for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Geronimo Tomcat fork 7.0.39.2 for a security fix
+1. Thanks! Jarek On Fri, May 17, 2013 at 2:06 AM, Forrest Xia wrote: > Hi, > > Please revote for the Geronimo Tomcat fork 7.0.39.2 release, which merges a > tomcat security fix for CVE-2013-2071 > > The components up for vote are: > https://repository.apache.org/content/repositories/orgapachegeronimo-008/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.2/tomcat-parent-7.0.39-7.0.39.2-source-release.zip > > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-008 > > tag is here: > http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.2 > > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > -- > Thanks! > > Regards, Forrest
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659765#comment-13659765 ] Jarek Gawor commented on GERONIMO-6451: --- Committed some JPA 2.1 updates in revision 1483469. > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar > > > Updated JPA 2.1 jar for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659650#comment-13659650 ] Jarek Gawor commented on GERONIMO-6451: --- In revision 1483415 I setup a new geronimo-jpa_2.1_spec project (copied from 2.0) - see https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jpa_2.1_spec/ (svn location). Can you please submit your 2.1 updates as a patch against this code? > API jar for JSR 338 - JPA 2.1 > - > > Key: GERONIMO-6451 > URL: https://issues.apache.org/jira/browse/GERONIMO-6451 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Kevin Sutter > Attachments: geronimo-jpa_2.1_spec-1.0.jar, > geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar > > > Updated JPA 2.1 jar for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Time for a new Geronimo 3 release?
I'm ok with trying 7.0.40. If it takes more then a week to resolve any potential regressions we can always switch back to 7.0.39 quickly. Alternatively, we can also port back specific fixes from 7.0.40 to our 7.0.39. Jarek On Thu, May 16, 2013 at 12:09 AM, Forrest Xia wrote: > 7.0.40 may bring in unexpected tck issue. We just hited and fixed a tck > regression brought by 7.0.39 upgrade. Since now the tck is in good shape, I > would prefer to make 3.0.1 release based on the validated 7.0.39 fork first. > thoughts? > > > On Thu, May 16, 2013 at 11:37 AM, Kevan Miller > wrote: >> >> >> On May 12, 2013, at 10:29 PM, Forrest Xia wrote: >> >> > Tomcat fork 7.0.39.1 is out, shall we start release of 3.0.1? Anything >> > more to add, please comment it on, or I will start the release process >> > around May 16. >> >> Unless I'm mistaken, looks like we'll need to move up to 7.0.40. >> >> --kevan > > > > > -- > Thanks! > > Regards, Forrest
Re: [VOTE] Release Geronimo Tomcat fork 7.0.39.1
+1 Jarek On Thu, May 9, 2013 at 10:41 PM, Forrest Xia wrote: > Hi, > > Please revote for the Geronimo Tomcat 7.0.39.1 release, which is based on > Tomcat 7.0.39 tag. > > The components up for vote are: > https://repository.apache.org/content/repositories/orgapachegeronimo-029/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.1/tomcat-parent-7.0.39-7.0.39.1-source-release.zip > > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-029 > > tag is here: > https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.1 > > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > -- > Thanks! > > Regards, Forrest
Re: Time for a new Geronimo 3 release?
Yes, current set of dependencies. I'm worried that once we start upgrading the versions of the various dependencies it will take weeks or months to resolve the problems caused by the upgrade. So for now I would rather focus on getting something out especially since things appear to be in a decent shape. Of course, if there is something that can be upgraded and it doesn't cause a lot of problems or additional work - I'm all for it. Jarek On Wed, May 8, 2013 at 3:25 PM, Kevan Miller wrote: > > On May 8, 2013, at 3:00 PM, Jarek Gawor wrote: > >> Hi all, >> >> I think it's probably a good time to have a new Geronimo 3 release >> (3.0.1?). We've fixed a bunch of stuff, upgraded Tomcat, OpenJPA, and >> fixed Java 7 complication issues. TCK is also looking pretty good now. >> >> Thoughts? > > Sounds great to me. I assume this is with the current set of dependencies? > E.g. OpenEJB 4.0.0-beta-1, xbean 3.11.1, myfaces 2.1.11, etc… > > Would be good to run a similar email by the user list… > > --kevan >
Re: [VOTE] Release Geronimo Tomcat 7.0.39.1
+1 - looks good to me. Thanks! Jarek On Thu, May 9, 2013 at 12:15 PM, Forrest Xia wrote: > Hi, > > Please vote for the Geronimo Tomcat 7.0.39.1 release, which is based on > Tomcat 7.0.39 tag. > > The components up for vote are: > https://repository.apache.org/content/repositories/orgapachegeronimo-026/org/apache/geronimo/ext/tomcat/tomcat-parent-7.0.39/7.0.39.1/tomcat-parent-7.0.39-7.0.39.1-source-release.zip > > > Staging repo is here: > https://repository.apache.org/content/repositories/orgapachegeronimo-026 > > tag is here: > https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-7.0.39.1 > > > Vote open 72 hours > > [ ] +1 release this > [ ] 0 don't care > [ ] -1 don't release this (please explain) > > -- > Thanks! > > Regards, Forrest
Time for a new Geronimo 3 release?
Hi all, I think it's probably a good time to have a new Geronimo 3 release (3.0.1?). We've fixed a bunch of stuff, upgraded Tomcat, OpenJPA, and fixed Java 7 complication issues. TCK is also looking pretty good now. Thoughts? Jarek
[jira] [Commented] (GERONIMODEVTOOLS-810) Server status not updated as server hostname is changed in server configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647688#comment-13647688 ] Jarek Gawor commented on GERONIMODEVTOOLS-810: -- Fixes committed (with other minor connection management improvements) in revision 1478439. > Server status not updated as server hostname is changed in server > configuration > > > Key: GERONIMODEVTOOLS-810 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Here's are the steps to demonstrate the issue: > 1) Stat a local server - serer status should be [Started] > 2) Edit server configuration and change hostname to specify a server on a > remote host. The remote server should be stopped. > The server status should eventually be updated to [Stopped] but it does not > change. > That's happening because GEP cached a connection to the local server and > won't release it until the local server is stopped somehow. Once the cached > connection is released the server status will reflect the right status of the > remote server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMODEVTOOLS-810) Server status not updated as server hostname is changed in server configuration
Jarek Gawor created GERONIMODEVTOOLS-810: Summary: Server status not updated as server hostname is changed in server configuration Key: GERONIMODEVTOOLS-810 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's are the steps to demonstrate the issue: 1) Stat a local server - serer status should be [Started] 2) Edit server configuration and change hostname to specify a server on a remote host. The remote server should be stopped. The server status should eventually be updated to [Stopped] but it does not change. That's happening because GEP cached a connection to the local server and won't release it until the local server is stopped somehow. Once the cached connection is released the server status will reflect the right status of the remote server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: update dependencies?
Updating dependencies sometimes can be a lot of work. So as long as updating OpenJPA /. OpenEJB doesn't cause a lot headaches I'm all for it. But in short term I think we should be concentrating on getting a new 3.0 release out. Jarek On Tue, Apr 23, 2013 at 8:45 AM, Kevan Miller wrote: > I see there is a new OpenJPA release. I also noticed that our OpenEJB > depencency is 4.0.0-beta-1. > > Any plans on updating these (or other dependencies)? > > --kevan
[jira] [Resolved] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6319. --- Resolution: Fixed Performance improvement committed in revision 1469337. > Discover and provision fragment bundles during OSGi application resolution > -- > > Key: GERONIMO-6319 > URL: https://issues.apache.org/jira/browse/GERONIMO-6319 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for discovering and provisioning fragment bundles during OSGi > application resolution. The application resolver will look for one fragment > per application bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reopened GERONIMO-6319: --- A performance problem was discovered when fragment bundles are being OBR resolved. Instead of resolving just the discovered fragment bundles, the current code resolves the application content and the fragment bundles. Basically, the application content is being resolved twice. > Discover and provision fragment bundles during OSGi application resolution > -- > > Key: GERONIMO-6319 > URL: https://issues.apache.org/jira/browse/GERONIMO-6319 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for discovering and provisioning fragment bundles during OSGi > application resolution. The application resolver will look for one fragment > per application bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6446. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as I think the key issues with building with Java 7 have been addressed. > Build with Java 7 > - > > Key: GERONIMO-6446 > URL: https://issues.apache.org/jira/browse/GERONIMO-6446 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635160#comment-13635160 ] Jarek Gawor commented on GERONIMO-6446: --- Ok, I changed the logic in revision 1469316. > Build with Java 7 > - > > Key: GERONIMO-6446 > URL: https://issues.apache.org/jira/browse/GERONIMO-6446 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633235#comment-13633235 ] Jarek Gawor commented on GERONIMO-6446: --- In revision 1468573 I committed additional changes that hopefully should make this error go away on Apple Java 7. Please verify. > Build with Java 7 > - > > Key: GERONIMO-6446 > URL: https://issues.apache.org/jira/browse/GERONIMO-6446 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630901#comment-13630901 ] Jarek Gawor commented on GERONIMO-6446: --- Looks like this is a known issue in the jspc plugin - see https://jira.codehaus.org/browse/MJSPC-53. There is a work-around but there is no fixed version of the plugin. > Build with Java 7 > - > > Key: GERONIMO-6446 > URL: https://issues.apache.org/jira/browse/GERONIMO-6446 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-706. -- Resolution: Fixed Fix Version/s: 3.0.1 This feature is implemented now. > Consider enabling Karaf shell in Eclipse console > > > Key: GERONIMODEVTOOLS-706 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-M2 >Reporter: Jarek Gawor >Assignee: Ted Kirby > Fix For: 3.0.1 > > Attachments: enableKarafShell_706_m0.patch, > enableKarafShell_706_m1.patch, enableKarafShell_706.patch, > karafSSHTerminal_improvement.jpg, karafSSHTerminal.jpg > > > (If possible) I think it would be pretty nice to have an option to enable and > access Karaf shell directly in Eclipse console window. If that can be done > make sure to start Geronimo server with > -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-762. -- Resolution: Fixed Resolving as the latest deployable and p2 zip are now automatically published after each change at https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/devtools/assembly/ > GEP needs a nightly builds repositary > - > > Key: GERONIMODEVTOOLS-762 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 > Project: Geronimo-Devtools > Issue Type: Wish > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Yi Xiao >Assignee: Yi Xiao > Labels: build, gep,, nightly > Attachments: gep_nightly_build_new.patch > > > The GEP had a nightly build repo before(refer to: > http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), > but it does not work now. So, I thought we should set up a environment to > redo it. > I've attached a patch to resolve the issue temporally. If you want to test it > in your local environment, should add below content to your maven's > settings.xml file: > > geronimo-devtools-nightly-repo > people.apache.org.username > people.apache.org.password > > Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-714) Synchronize the server configuration between GEP and server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-714. -- Resolution: Duplicate This is duplicate of GERONIMODEVTOOLS-795. > Synchronize the server configuration between GEP and server > --- > > Key: GERONIMODEVTOOLS-714 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 2.2.1, 2.1.7, 3.0 >Reporter: Han Hong Fang > > Currently GEP has server configuration such as administrator id, > administrator password, HTTP port value and RMI Naming port value. These are > set with default values when server is created. Although the values can be > modified during server creation or after server creation, this can be > improved by reading such values from server configuration files when runtime > is located on local machine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-695) Synchronize dependency version with Geronimo 3.0 M2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-695. -- Resolution: Fixed This is/was already done. > Synchronize dependency version with Geronimo 3.0 M2 > --- > > Key: GERONIMODEVTOOLS-695 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-M2 >Reporter: Han Hong Fang >Assignee: Han Hong Fang > Fix For: 3.0-M2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-235) Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-235. -- Resolution: Fixed Fix Version/s: (was: 2.2.2) 3.0.1 WIth GERONIMODEVTOOLS-795 GEP will tell the server what ports to use. > Plugin cannot synchronize with the server when non-zero portOffset value in > the config-substitutions.properties file > > > Key: GERONIMODEVTOOLS-235 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.0.0 >Reporter: Tim McConnell > Fix For: 3.0.1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6319. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. > Discover and provision fragment bundles during OSGi application resolution > -- > > Key: GERONIMO-6319 > URL: https://issues.apache.org/jira/browse/GERONIMO-6319 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for discovering and provisioning fragment bundles during OSGi > application resolution. The application resolver will look for one fragment > per application bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6397) Improve resolver-based error messages for OSGi application
[ https://issues.apache.org/jira/browse/GERONIMO-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6397. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. > Improve resolver-based error messages for OSGi application > -- > > Key: GERONIMO-6397 > URL: https://issues.apache.org/jira/browse/GERONIMO-6397 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Improve ResolverErrorAnalyzer for OSGi applications. Specifically in cases > where a import package cannot be satisfied provide details if the given > package is exported by any bundles or if there are bundles that export that > package with different version, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6434) in-place deployment for OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6434. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as in-place deployment of OSGi applications seems to be working now. > in-place deployment for OSGi applications > - > > Key: GERONIMO-6434 > URL: https://issues.apache.org/jira/browse/GERONIMO-6434 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for in-place deployment of OSGi applications. That is, the > contents of the .eba archive and its bundles are expanded on disk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5231) Override JVM libraries with newer versions
[ https://issues.apache.org/jira/browse/GERONIMO-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5231. --- Resolution: Fixed Fix Version/s: (was: 3.0.1) 3.0.0 This was done/enabled a while ago. Forgot to close it. > Override JVM libraries with newer versions > -- > > Key: GERONIMO-5231 > URL: https://issues.apache.org/jira/browse/GERONIMO-5231 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.0 > > > In some cases, Java EE 6 requires newer library versions then what is > provided by Java SE 6. For example, EE 6 requires annotations 1.1 api but SE > 6 provides annotation 1.0 api. So it is necessary that during a build we > override the JVM provided libraries with newer versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5166) Enable car-maven-plugin to use Equinox
[ https://issues.apache.org/jira/browse/GERONIMO-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5166. --- Resolution: Fixed Fix Version/s: 3.0.0 Resolving as this is done and we are / were building with Equinox for a while. > Enable car-maven-plugin to use Equinox > -- > > Key: GERONIMO-5166 > URL: https://issues.apache.org/jira/browse/GERONIMO-5166 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) > Components: car-maven-plugin >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1, 3.0.0 > > > Ability for car-maven-plugin to switch between Felix or Equinox as the OSGi > framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6445) Support configuration imports
[ https://issues.apache.org/jira/browse/GERONIMO-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6445. --- Resolution: Fixed Fix Version/s: 3.0.1 > Support configuration imports > -- > > Key: GERONIMO-6445 > URL: https://issues.apache.org/jira/browse/GERONIMO-6445 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: kernel >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for configuration imports for config.properties and > system.properties files. That will make it simpler to have separate > configuration files for command line tools and server without duplicating the > configuration information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6417) Launch listener
[ https://issues.apache.org/jira/browse/GERONIMO-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6417. --- Resolution: Fixed Fix Version/s: 3.0.1 > Launch listener > --- > > Key: GERONIMO-6417 > URL: https://issues.apache.org/jira/browse/GERONIMO-6417 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Add support for launch listeners. This is so that one can register a listener > to receive events about launcher starting and stopping the runtime in order > to perform custom action based on those events. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (XBEAN-242) Potential file descriptor leak in BundleResourceFinder
[ https://issues.apache.org/jira/browse/XBEAN-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor closed XBEAN-242. - Resolution: Fixed Fix Version/s: 3.13 Fixed. > Potential file descriptor leak in BundleResourceFinder > -- > > Key: XBEAN-242 > URL: https://issues.apache.org/jira/browse/XBEAN-242 > Project: XBean > Issue Type: Bug > Components: bundleutils >Affects Versions: 3.12 > Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.13 > > > BundleResourceFinder opens ZipInputStream but never explicitly closes it. > That can potentially lead to file descriptor leaks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-795. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as it works as expected. > Synchronizing port configuration > > > Key: GERONIMODEVTOOLS-795 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 > Project: Geronimo-Devtools > Issue Type: Improvement > Components: eclipse-plugin >Affects Versions: 3.0-beta-1 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Currently, GEP keep its own port configuration, separate from the server's > configuration. The port information between GEP & server is not synchronized > in any way. And sometimes as the port information between the server & GEP > becomes out of synch, it creates problems for users when starting or > deploying modules to the server from GEP. > It would be nice to update the GEP to keep the port information in synch with > the server. That is, if the server configuration is changed, that change is > reflected in GEP. And if the change in made in GEP, the server configuration > is updated as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-809. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as the new port checking seems to be working as expected. > In-use port detection does not work sometimes > - > > Key: GERONIMODEVTOOLS-809 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 3.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 3.0.1 > > > Before starting a server, GEP checks if the http and naming ports are free. > This check does not work sometimes on some platforms (e.g. Windows). That's > because on Windows it is possible to bind to 0.0.0.0 (any/all network > interfaces) and 127.0.0.1 with the same port at the same time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6443) Bundles resolve even though "package uses conflict" error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6443. --- Resolution: Fixed Resolving as the work-around seems to be working ok. > Bundles resolve even though "package uses conflict" error is reported during > EBA deployment > > > Key: GERONIMO-6443 > URL: https://issues.apache.org/jira/browse/GERONIMO-6443 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0.0 >Reporter: Jarek Gawor >Assignee: Jarek Gawor > > During EBA deployment "uses directive conflict" errors are reported and the > given bundles are left in Installed state. However, starting or resolving the > bundles again is successful (and the bundles move to Active or Resolved > state). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6448) "Configuration already exists" error when redeploying OSGi application
[ https://issues.apache.org/jira/browse/GERONIMO-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629325#comment-13629325 ] Jarek Gawor commented on GERONIMO-6448: --- Looks like there is a bug Aries' BundleManifest.fromBundle(File) function. It doesn't close the input stream if the file argument is a directory. In revision 1467077 I committed a fix (on Geronimo side) for this issue - it ensures we always close the input stream. > "Configuration already exists" error when redeploying OSGi application > -- > > Key: GERONIMO-6448 > URL: https://issues.apache.org/jira/browse/GERONIMO-6448 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Aries >Affects Versions: 3.0.0 > Environment: Windows 7 > Reporter: Jarek Gawor >Assignee: Jarek Gawor > > Here's how to replicate the problem on Windows using GEP: > 1. Publish OSGi application which has dependency problems. > 2. Start server and get publish errors. > 3. Right click this application in Servers view and remove it. > 4. Right click server and add the application again. Then this error happens. > Following is the error generated: > org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: > Configuration already exists: application/test.eba/1.0.0-qualifier/eba > org.apache.geronimo.common.DeploymentException: > org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: > Configuration already exists: application/test.eba/1.0.0-qualifier/eba -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6448) "Configuration already exists" error when redeploying OSGi application
Jarek Gawor created GERONIMO-6448: - Summary: "Configuration already exists" error when redeploying OSGi application Key: GERONIMO-6448 URL: https://issues.apache.org/jira/browse/GERONIMO-6448 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Environment: Windows 7 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's how to replicate the problem on Windows using GEP: 1. Publish OSGi application which has dependency problems. 2. Start server and get publish errors. 3. Right click this application in Servers view and remove it. 4. Right click server and add the application again. Then this error happens. Following is the error generated: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba org.apache.geronimo.common.DeploymentException: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
