Back to bug 1011918

Who When What Removed Added
Rostislav Svoboda 2013-09-25 11:52:48 UTC Keywords Regression
Vladimir Dosoudil 2013-09-25 12:01:26 UTC CC dosoudil
Assignee pgier lgao
Lin Gao 2013-09-26 03:18:33 UTC Status NEW POST
Target Milestone --- ER4
Pavel Slavicek 2013-09-27 08:41:06 UTC Blocks 1010473
Rostislav Svoboda 2013-09-27 11:53:21 UTC Status POST ASSIGNED
Brian Stansberry 2013-09-27 13:46:59 UTC CC brian.stansberry
Lin Gao 2013-09-29 03:02:38 UTC Assignee lgao pgier
Alessio Soldano 2013-09-30 13:07:36 UTC CC asoldano
mark yarborough 2013-09-30 14:25:08 UTC CC myarboro
Blocks 1010473
Doc Text Needs to be a known issue / workaround for Beta; Should be better fix for GA...
Cause:

Consequence:

Fix:

Result:
Brian Stansberry 2013-10-01 12:24:12 UTC Status ASSIGNED MODIFIED
Vladimir Dosoudil 2013-10-04 06:55:31 UTC Status MODIFIED ON_QA
Target Release --- EAP 6.2.0
Nikoleta Hlavickova 2013-10-07 10:51:53 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1016027
Brian Stansberry 2013-10-07 16:05:33 UTC CC brian.stansberry
Rostislav Svoboda 2013-10-08 12:44:19 UTC Status ON_QA VERIFIED
Lin Gao 2013-10-22 09:39:38 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=999846
Paul Gier 2013-11-20 13:59:17 UTC Doc Text Needs to be a known issue / workaround for Beta; Should be better fix for GA...
Cause:

Consequence:

Fix:

Result:
Cause: The EAP build process was changed to provide more conventional Maven POM files (more consistent to community Maven POMs)

Consequence: The POM files in the EAP Maven repository have dependencies on some community artifact versions.

Fix: Configure the appropriate Maven BOM file documented in the developer's guide.

Result: Configuring the appropriate Maven BOM file will ensure that the user build includes the correct transitive dependency version (i.e. eap version for supported artifacts and community version for unsupported artifacts).
Scott Mumford 2013-11-20 21:06:09 UTC CC smumford
Doc Text Cause: The EAP build process was changed to provide more conventional Maven POM files (more consistent to community Maven POMs)

Consequence: The POM files in the EAP Maven repository have dependencies on some community artifact versions.

Fix: Configure the appropriate Maven BOM file documented in the developer's guide.

Result: Configuring the appropriate Maven BOM file will ensure that the user build includes the correct transitive dependency version (i.e. eap version for supported artifacts and community version for unsupported artifacts).
The build process was changed in this release of JBoss EAP to provide more conventional Maven POM files which are more consistent with community Maven POMs. The POM files in the EAP Maven repository now have dependencies on some community artifact versions.

Users should refer to the JBoss Enterprise Application Platform Developer Guide for information on how to configure the appropriate Maven BOM file. Configuring the appropriate Maven BOM file will ensure that the user build includes the correct transitive dependency version (the JBoss EAP version will be used for supported artifacts and the community version for unsupported artifacts).
mark yarborough 2013-12-15 16:13:37 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2013-12-15 11:13:37 UTC

Back to bug 1011918