Fwd: Cannot check in code to apache tck repo, why?
Not only I cannot check in to apache tck repo, but also cannot check in to the general repo. Is the apache svn repo in maintainence?? or my committer password expired? -- Forwarded message -- From: Forrest Xia forres...@gmail.com Date: Thu, May 16, 2013 at 1:34 PM Subject: Cannot check in code to apache tck repo, why? To: Geronimo Certification Effort geronimo-...@geronimo.apache.org, priv...@geronimo.apache.org, infrastruct...@apache.org, infrastructure-priv...@apache.org Today when I want o make 3.0.1 tck tag, I met problem when doing commit. I confirm I inputted the correct password, but it always prompt me it's wrong. Why this happens? -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest
Re: Cannot check in code to apache tck repo, why?
Finally I reset my password via id.apache.org, then it works now. On Thu, May 16, 2013 at 2:01 PM, Forrest Xia forres...@gmail.com wrote: Not only I cannot check in to apache tck repo, but also cannot check in to the general repo. Is the apache svn repo in maintainence?? or my committer password expired? -- Forwarded message -- From: Forrest Xia forres...@gmail.com Date: Thu, May 16, 2013 at 1:34 PM Subject: Cannot check in code to apache tck repo, why? To: Geronimo Certification Effort geronimo-...@geronimo.apache.org, priv...@geronimo.apache.org, infrastruct...@apache.org, infrastructure-priv...@apache.org Today when I want o make 3.0.1 tck tag, I met problem when doing commit. I confirm I inputted the correct password, but it always prompt me it's wrong. Why this happens? -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest -- Thanks! Regards, Forrest
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 forres...@gmail.com 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 kevan.mil...@gmail.com wrote: On May 12, 2013, at 10:29 PM, Forrest Xia forres...@gmail.com 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
[jira] [Updated] (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 ] Pinaki Poddar updated GERONIMO-6451: Attachment: geronimo-jpa_2.1_spec-1.0.jar Source files for JSR-338 JPA 2.1 Specification. 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 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] [Issue Comment Deleted] (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 ] Pinaki Poddar updated GERONIMO-6451: Comment: was deleted (was: Source files for JSR-338 JPA 2.1 Specification. ) 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] [Updated] (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 ] Pinaki Poddar updated GERONIMO-6451: Attachment: geronimo-jpa_2.1_spec-1.0-src.jar geronimo-jpa_2.1_spec-1.0.jar Compiled library and source files for JSR-338 (JPA) Specification version 2.1. 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?
On May 16, 2013, at 10:22 AM, Jarek Gawor jga...@gmail.com wrote: 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. I'm fine with either approach. If a patched 7.0.39 is simpler, then do that… --kevan
[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-tabpanelfocusedCommentId=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
[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-tabpanelfocusedCommentId=13659652#comment-13659652 ] Kevan Miller commented on GERONIMO-6451: Hi Pinaki, I assume that you've created the source in geronimo-jpa_2.1_spec-1.0-src.jar? Is there a reason why this source is not built from our 2.0 source (i.e. https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jpa_2.0_spec). BTW, we'd be happy to svn copy geronimo-jpa_2.0_spec to geronimo-jpa_2.1_spec... 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-tabpanelfocusedCommentId=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] [Created] (GERONIMO-6468) Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork
Forrest Xia created GERONIMO-6468: - Summary: Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork Key: GERONIMO-6468 URL: https://issues.apache.org/jira/browse/GERONIMO-6468 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0.1 Reporter: Forrest Xia Assignee: Forrest Xia Fix For: 3.0.1 Need to pull in a tomcat security fix into 7.0.39 fork for G 3.0.1 release -- 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-6468) Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork
[ https://issues.apache.org/jira/browse/GERONIMO-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660212#comment-13660212 ] Forrest Xia commented on GERONIMO-6468: --- Jarek has done this port back at r1483405, thanks! Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork Key: GERONIMO-6468 URL: https://issues.apache.org/jira/browse/GERONIMO-6468 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0.1 Reporter: Forrest Xia Assignee: Forrest Xia Fix For: 3.0.1 Need to pull in a tomcat security fix into 7.0.39 fork for G 3.0.1 release -- 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-6468) Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork
[ https://issues.apache.org/jira/browse/GERONIMO-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6468. --- Resolution: Fixed Assignee: Jarek Gawor (was: Forrest Xia) Pull the fix for tomcat security hole CVE-2013-2071 into 7.0.39 fork Key: GERONIMO-6468 URL: https://issues.apache.org/jira/browse/GERONIMO-6468 Project: Geronimo Issue Type: Task Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0.1 Reporter: Forrest Xia Assignee: Jarek Gawor Fix For: 3.0.1 Need to pull in a tomcat security fix into 7.0.39 fork for G 3.0.1 release -- 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
