Re: [VOTE] Release geronimo-jaxws_2.2_spec-1.2
All looks good to me: sigs/checksum, source/rat, license/notice, build… +1 --kevan On Mar 29, 2013, at 11:15 PM, Jarek Gawor jga...@gmail.com wrote: Hi all, I would like to call a vote on geronimo-jaxws_2.2_spec-1.2. It is a minor release that contains GERONIMO-6432. Source archives: https://repository.apache.org/content/repositories/orgapachegeronimo-037/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.2/ Source tag: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaxws_2.2_spec-1.2 Staging repository: https://repository.apache.org/content/repositories/orgapachegeronimo-037/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1. Jarek
[VOTE RESULT] Release geronimo-jaxws_2.2_spec-1.2
Hi all, Here are the vote results: +1: Kevan, Ivan, Shawn, Jarek +0: none -1: none The vote passes. I'll get the artifacts published. Thank you all, Jarek
[VOTE] (take 2) Release yoko-1.4
Hi all, I would like to call a vote on yoko-1.4. It is a minor release that contains TCK related fixes (GERONIMOTCK-133, GERONIMOTCK-142) and Genesis update to build with Java 7. Source archives: https://repository.apache.org/content/repositories/orgapachegeronimo-052/org/apache/yoko/yoko/1.4/ Source tag: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.4/ Staging repository: https://repository.apache.org/content/repositories/orgapachegeronimo-052/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1. Jarek
Re: [VOTE] (take 2) Release yoko-1.4
Looks good to me. Sig/checksum, source/RAT, LICENSE/NOTICE, build… Here's my +1 Thanks Jarek! --kevan On Apr 2, 2013, at 11:07 AM, Jarek Gawor jga...@gmail.com wrote: Hi all, I would like to call a vote on yoko-1.4. It is a minor release that contains TCK related fixes (GERONIMOTCK-133, GERONIMOTCK-142) and Genesis update to build with Java 7. Source archives: https://repository.apache.org/content/repositories/orgapachegeronimo-052/org/apache/yoko/yoko/1.4/ Source tag: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.4/ Staging repository: https://repository.apache.org/content/repositories/orgapachegeronimo-052/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1. Jarek
[jira] [Created] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
Jarek Gawor created GERONIMO-6443: - Summary: 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. -- 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-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 updated GERONIMO-6443: -- Description: 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). was: 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. 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-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:comment-tabpanelfocusedCommentId=13620166#comment-13620166 ] Jarek Gawor commented on GERONIMO-6443: --- With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. But forcing bundle resolution again seems to work 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] [Comment Edited] (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:comment-tabpanelfocusedCommentId=13620166#comment-13620166 ] Jarek Gawor edited comment on GERONIMO-6443 at 4/2/13 7:36 PM: --- With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. This timeout can be increased by setting osgi.usesTimeout property (it's 30 seconds by default). However, setting it to something larger then 30 seconds or making it unlimited doesn't really help as Equinox just keeps looking for a better solution. However, forcing bundle resolution again (after the first try) seems to work ok. was (Author: ga...@mcs.anl.gov): With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. But forcing bundle resolution again seems to work 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-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:comment-tabpanelfocusedCommentId=13620172#comment-13620172 ] Jarek Gawor commented on GERONIMO-6443: --- Committed changed in revision 1463715 to perform bundle resolution twice to work-around this problem. 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
