Bug 1121630 - [GSS] (6.3.1) Upgrade Hibernate-ORM from 4.2.14.SP1-redhat-1 to 4.2.14.SP2
Summary: [GSS] (6.3.1) Upgrade Hibernate-ORM from 4.2.14.SP1-redhat-1 to 4.2.14.SP2
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: CR1
: EAP 6.3.1
Assignee: Dave Stahl
QA Contact: Martin Simka
Russell Dickenson
Depends On: 1092175 1094955 1102974 1117447 1118373 1121629 1126959 1130668
Blocks: eap631-blockers, eap631-payload, eap63-cp01-blockers
TreeView+ depends on / blocked
Reported: 2014-07-21 12:14 UTC by Jimmy Wilson
Modified: 2015-11-09 01:11 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1121629
Last Closed: 2014-10-13 18:37:54 UTC
Type: Component Upgrade

Attachments (Terms of Use)

Description Jimmy Wilson 2014-07-21 12:14:44 UTC
+++ This bug was initially created as a clone of Bug #1121629 +++

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Gail Badner 2014-08-15 21:19:24 UTC
This component upgrade should also depend on a clone of 1111630 for 6.3.1.

Comment 2 Gail Badner 2014-08-15 23:45:41 UTC
I've cherry-picked the commits from upstream 4.2 branch and pushed to http://git.app.eng.bos.redhat.com/git/hibernate/hibernate-core.git/log/?h=4.2.14.SP2-redhat

Comment 3 baranowb 2014-08-18 05:41:36 UTC
In such case, I'm assigning this to vtunka for prod build.

Comment 6 baranowb 2014-08-18 17:07:39 UTC
Great. Thanks Dave.

Comment 7 baranowb 2014-08-19 15:21:31 UTC

Comment 8 Dave Stahl 2014-08-27 23:51:37 UTC
A regression was found in 4.2.14.SP2 which will require a new build for 6.3.1.  Upgrade version will be 4.2.14.SP3-redhat-1

Comment 9 Vladimir Dosoudil 2014-08-28 05:34:49 UTC
CR1 is already available, the upgrade to 4.2.14.SP3 must be done in CR2.

Comment 16 Jan Martiska 2014-08-29 07:49:02 UTC
Verified in EAP 6.3.1.CR1.

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