Bug 1196113 - [6.4.z] Upgrade hibernate ORM from 4.2.18.Final-redhat-2 to 4.2.19.Final-redhat-1
Summary: [6.4.z] Upgrade hibernate ORM from 4.2.18.Final-redhat-2 to 4.2.19.Final-redh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.2
Assignee: Gail Badner
QA Contact: Martin Simka
URL:
Whiteboard:
Depends On: 1170257 1189305 1197261 1211402
Blocks: 1219165
TreeView+ depends on / blocked
 
Reported: 2015-02-25 10:39 UTC by baranowb
Modified: 2017-01-17 10:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Component Upgrade
Embargoed:
gbadner: needinfo+

Attachments (Terms of Use)

Description baranowb 2015-02-25 10:39:51 UTC
Comment 1 Gail Badner 2015-03-09 19:51:46 UTC 
The only dependency I see currently is https://bugzilla.redhat.com/show_bug.cgi?id=1170257. That fix is for ORM, not Validator.

Is there any other reason to upgrade Validator?
Comment 2 Gail Badner 2015-03-09 20:07:26 UTC 
If Validator does not need to be upgraded, then please change this BZ to upgrade ORM from 4.2.18.Final-redhat-1 to 4.2.19.Final-redhat-1.

There is another BZ that should be included in 4.2.19.Final-redhat-1 as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1189305
Comment 4 Dave Stahl 2015-05-01 12:17:36 UTC 
Upstream tag: https://github.com/hibernate/hibernate-orm/releases/tag/4.2.19.Final
Comment 12 Martin Simka 2015-06-22 14:40:24 UTC 
verified
EAP 6.4.2.CP.CR1
Comment 13 Petr Penicka 2017-01-17 10:18:41 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 14 Petr Penicka 2017-01-17 10:18:42 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 15 Petr Penicka 2017-01-17 10:18:56 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Note You need to log in before you can comment on or make changes to this bug.