Bug 1082820

Summary:	Explicitly define all runtime dependency versions
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Paul Gier <pgier>
Component:	Build	Assignee:	Paul Gier <pgier>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Jelinek <pjelinek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	kkhan
Target Milestone:	ER1
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 14:39:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Gier 2014-03-31 21:33:28 UTC

All runtime dependency versions should be explicitly defined in the jboss-as-parent pom.  This provides an easy reference for current dep versions and ensures that there are no unexpected dependency upgrades.

Comment 1 Paul Gier 2014-04-01 17:45:39 UTC

The reason this popped up is because a runtime dependency (apache commons-net) which was relying on the external BOM to define its version.  This dependency was introduced in a separate commit from the one that added the BOM.

6.x PR: https://github.com/jbossas/jboss-eap/pull/1171

Comment 2 Pavel Jelinek 2014-04-16 06:43:47 UTC

Done in EAP 6.3.0.ER1