Bug 1082820 - Explicitly define all runtime dependency versions
Summary: Explicitly define all runtime dependency versions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Build
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.3.0
Assignee: Paul Gier
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-31 21:33 UTC by Paul Gier
Modified: 2014-08-06 14:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 14:39:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3199 0 Minor Resolved Remove external BOM from jboss-as-parent 2016-03-23 20:39:15 UTC

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
Note You need to log in before you can comment on or make changes to this bug.