[Vote] Geronimo Eclipse Plugin (GEP) 2.1.8 RC1
Hi devs, With great help of Yi Xiao, I made a stage repo for GEP 2.1.8 release vote. So everyone, please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 2.1.8 RC1 from now on. GEP 2.1.8 supports Geronimo server 2.1.8 and Eclipse Indigo SR1(3.7.1). The source code zip is here: * https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.tar.gz * * https://repository.apache.org/content/repositories/orgapachegeronimo-016/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.8/geronimo-eclipse-plugin-2.1.8-source-release.zip * The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-2.1.8 The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-deployable.zip The update site zip file is here: http://people.apache.org/builds/geronimo/eclipse/2.1.8/geronimo-eclipse-plugin-2.1.8-updatesite.zip If you would like to review and/or comment on the release notes, you can find it here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-2.1.8.txt Create a Staging Site that can be used to test the update manager functions of Eclipse (Indigo and helios): http://people.apache.org/builds/geronimo/eclipse/updates/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Thanks! Regards, Forrest
[jira] [Assigned] (GERONIMO-6193) NPE exception in org.apache.catalina.connector.CoyoteAdapter.service
[ https://issues.apache.org/jira/browse/GERONIMO-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-6193: - Assignee: xiezhi > NPE exception in org.apache.catalina.connector.CoyoteAdapter.service > > > Key: GERONIMO-6193 > URL: https://issues.apache.org/jira/browse/GERONIMO-6193 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 3.0 >Reporter: viola.lu >Assignee: xiezhi >Priority: Minor > Fix For: 3.0.1 > > > Open this jira to track > https://issues.apache.org/bugzilla/show_bug.cgi?id=52009, which is fixed in > tomcat and will be included in tomcat 7.0.23. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6250) Allow definition of maxParameterCount in gbean
[ https://issues.apache.org/jira/browse/GERONIMO-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6250. --- Resolution: Fixed Fix Version/s: 2.1.9 commit to 2.1@1227961 > Allow definition of maxParameterCount in gbean > -- > > Key: GERONIMO-6250 > URL: https://issues.apache.org/jira/browse/GERONIMO-6250 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1.8 >Reporter: Forrest Xia >Assignee: Forrest Xia > Fix For: 2.1.9 > > > maxParameterCount is a new parameter of Tomcat since 6.0.35, we need to > update the gbean to allow its definition in Geronimo way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6250) Allow definition of maxParameterCount in gbean
[ https://issues.apache.org/jira/browse/GERONIMO-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia reassigned GERONIMO-6250: - Assignee: Forrest Xia > Allow definition of maxParameterCount in gbean > -- > > Key: GERONIMO-6250 > URL: https://issues.apache.org/jira/browse/GERONIMO-6250 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.1.8 >Reporter: Forrest Xia >Assignee: Forrest Xia > > maxParameterCount is a new parameter of Tomcat since 6.0.35, we need to > update the gbean to allow its definition in Geronimo way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Geronimo 3 and karaf 3
yup, karaf just copied those classes into itself to avoid some java 7 problem just committed a fix along with some other work. david jencks On Jan 5, 2012, at 6:16 PM, Kevan Miller wrote: > > I'm seeing this same failure, locally -- > http://ci.apache.org/builders/geronimo-server-trunk/builds/498/steps/compile/logs/stdio > > Anyone else? > > --kevan
Re: Geronimo 3 and karaf 3
I'm seeing this same failure, locally -- http://ci.apache.org/builders/geronimo-server-trunk/builds/498/steps/compile/logs/stdio Anyone else? --kevan
[jira] [Updated] (GERONIMO-6253) Improve parameter handling patch from tomcat community for G 2.2.1 release
[ https://issues.apache.org/jira/browse/GERONIMO-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia updated GERONIMO-6253: -- Description: We need a fix for Geronimo 2.2.1 release for the parameter handling issue from Tomcat community. (was: We need a fix for Geronimo 2.2.x release for the tomcat security patch of CVE-2011-4084.) Summary: Improve parameter handling patch from tomcat community for G 2.2.1 release (was: Tomcat security patch of CVE-2011-4084 for G 2.2.1 release) > Improve parameter handling patch from tomcat community for G 2.2.1 release > -- > > Key: GERONIMO-6253 > URL: https://issues.apache.org/jira/browse/GERONIMO-6253 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 2.2, 2.2.1 >Reporter: Forrest Xia > > We need a fix for Geronimo 2.2.1 release for the parameter handling issue > from Tomcat community. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6254) Shared library does not work in the deployment process
[ https://issues.apache.org/jira/browse/GERONIMO-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180389#comment-13180389 ] Ivan commented on GERONIMO-6254: Commit changes to 3.0-beta branch at rev227586. > Shared library does not work in the deployment process > -- > > Key: GERONIMO-6254 > URL: https://issues.apache.org/jira/browse/GERONIMO-6254 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: deployment >Affects Versions: 3.0-beta-1 >Reporter: Ivan >Assignee: Ivan > Fix For: 3.0-beta-2 > > > In the deployment process, as the temp configuration is kept in the > DeploymentConfigurationManager, SharedLibExtender will not find its parents. > Will use DependencyManager to look up the dependent bundles instead. There > maybe issue in the trunk codes, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6254) Shared library does not work in the deployment process
Shared library does not work in the deployment process -- Key: GERONIMO-6254 URL: https://issues.apache.org/jira/browse/GERONIMO-6254 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0-beta-1 Reporter: Ivan Assignee: Ivan Fix For: 3.0-beta-2 In the deployment process, as the temp configuration is kept in the DeploymentConfigurationManager, SharedLibExtender will not find its parents. Will use DependencyManager to look up the dependent bundles instead. There maybe issue in the trunk codes, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
