Bug 1002584 - Upgrade JBoss Transactions to 4.17.9.Final
Upgrade JBoss Transactions to 4.17.9.Final
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Transaction Manager (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity unspecified
: ER1
: EAP 6.2.0
Assigned To: tom.jenkinson
Ondrej Chaloupka
:
Depends On: 992915 1001909 971358
Blocks: 1008322
  Show dependency treegraph
 
Reported: 2013-08-29 09:36 EDT by Ivo Studensky
Modified: 2017-10-09 20:26 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-12-15 11:55:24 EST
Type: Component Upgrade
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ivo Studensky 2013-08-29 09:36:06 EDT
Upgrade JBoss Transactions to 4.17.9.
Comment 2 tom.jenkinson 2013-08-30 12:03:44 EDT
6.x: https://github.com/jbossas/jboss-eap/pull/329
6.1.x: https://github.com/jbossas/jboss-eap/pull/330

I am trying to transition this to POST:
"For all JBoss bugs, it is mandatory to set the target milestone field to a non-empty value before a bug can be moved past the ASSIGNED state. i.e. to POST, MODIFIED, ON_DEV, ON_QA, VERIFIED or RELEASE_PENDING. "
Comment 3 Ivo Studensky 2013-08-30 14:23:12 EDT
PR for 6.x is enough for EAP 6.2. Thanks.
Comment 5 Ondrej Chaloupka 2013-09-18 05:13:00 EDT
Verified for 6.2.0.ER1.

Note You need to log in before you can comment on or make changes to this bug.