Bug 1009913

Summary:	RHEL 6 RPMs: Upgrade weld-core to 1.1.16.Final-redhat-1
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Vladimir Dosoudil <dosoudil>
Component:	RPMs	Assignee:	Vladimir Dosoudil <dosoudil>
Status:	CLOSED ERRATA	QA Contact:	Katerina Odabasi <kanovotn>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	fnasser, pgier
Target Milestone:	---	Keywords:	Rebase
Target Release:	EAP 6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-04 18:12:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimir Dosoudil 2013-09-19 13:30:48 UTC

Required upgrade.

Comment 1 Vladimir Dosoudil 2013-09-20 14:05:28 UTC

Source URL: 
Mead-Build: org.jboss.weld-weld-core-parent-1.1.15.Final_redhat_1-1
Brew-Build: weld-core-1.1.15-1.Final_redhat_1.1.ep6.el6

Comment 3 Vladimir Dosoudil 2013-09-30 09:36:11 UTC

Source URL: 
Mead-Build: org.jboss.weld-weld-core-parent-1.1.16.Final_redhat_1-1
Brew-Build: weld-core-1.1.16-1.Final_redhat_1.1.ep6.el6

Comment 4 Fernando Nasser 2013-09-30 20:14:35 UTC

Clarifying, we have 1.1.15 on both ER3 ZIP and RPMs, but weld-core has changed again to 1.1.16, which will only e available (ZIP and RPMs) on ER4.

Comment 5 Fernando Nasser 2013-10-04 15:27:16 UTC

RPMs not with QE yet.

Comment 6 Dustin Kut Moy Cheung 2013-10-04 18:21:18 UTC

Source URL: 
Mead-Build: org.jboss.weld-weld-core-parent-1.1.16.Final_redhat_1-1
Brew-Build: weld-core-1.1.16-3.Final_redhat_1.1.ep6.el6

Comment 7 Pavel Janousek 2013-10-15 12:06:32 UTC

Fine in ER5 build.

Comment 8 Pavel Janousek 2013-11-06 14:26:43 UTC

Fine in ER7 build.

Comment 10 errata-xmlrpc 2013-12-04 18:12:46 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1786.html