Back to bug 1004868

Who When What Removed Added
Brenton Leanhardt 2013-09-05 16:11:39 UTC Status NEW ASSIGNED
Target Release --- 1.2.3
Brenton Leanhardt 2013-09-06 15:07:26 UTC Blocks 1005281
Brenton Leanhardt 2013-09-06 17:19:41 UTC CC rlucente
Flags needinfo?(rlucente)
Rich Lucente 2013-09-06 19:26:59 UTC Flags needinfo?(rlucente)
Brenton Leanhardt 2013-09-10 20:00:07 UTC Status ASSIGNED MODIFIED
Brenton Leanhardt 2013-09-10 20:48:25 UTC Status MODIFIED ON_QA
Gaoyun Pei 2013-09-11 12:34:04 UTC Status ON_QA ASSIGNED
CC gpei
Brenton Leanhardt 2013-09-11 14:47:12 UTC Status ASSIGNED MODIFIED
Brenton Leanhardt 2013-09-11 20:24:52 UTC Status MODIFIED ON_QA
Fixed In Version openshift-origin-cartridge-jbosseap-2.3.11.2-1 openshift-origin-cartridge-jbossews-0.4.10-1
Gaoyun Pei 2013-09-12 02:41:51 UTC Status ON_QA VERIFIED
Brenton Leanhardt 2013-09-16 19:42:29 UTC Doc Text Cause:
Default pom template for JBoss EAP reference older JBoss EAP version. The EWS cartridge referenced the dependency but it was not needed.

Consequence:
In some cases it was merely confusing. In environment where only the latest EAP jars were available in the maven repository initial application builds could fail.

Fix:
Update the pom template for EAP. Remove the stale reference from the EWS cartridge.

Result:
Bilhar 2013-09-19 04:29:23 UTC CC baulakh
Doc Text Cause:
Default pom template for JBoss EAP reference older JBoss EAP version. The EWS cartridge referenced the dependency but it was not needed.

Consequence:
In some cases it was merely confusing. In environment where only the latest EAP jars were available in the maven repository initial application builds could fail.

Fix:
Update the pom template for EAP. Remove the stale reference from the EWS cartridge.

Result:
Previously the default pom template for JBoss EAP referenced an older version of JBoss EAP, and the EWS cartridge referenced a dependency that was not required. This was confusing for users, and in some cases initial application builds failed in environments where only the latest EAP jars were available in the maven repository. The EAP pom templates have been updated and this issue has been fixed in the current release of OpenShift Enterprise.
Bilhar 2013-09-20 01:01:19 UTC Doc Text Previously the default pom template for JBoss EAP referenced an older version of JBoss EAP, and the EWS cartridge referenced a dependency that was not required. This was confusing for users, and in some cases initial application builds failed in environments where only the latest EAP jars were available in the maven repository. The EAP pom templates have been updated and this issue has been fixed in the current release of OpenShift Enterprise. Previously the default pom template for JBoss EAP referenced an older version of JBoss EAP, and the EWS cartridge referenced a dependency that was not required. This was confusing for users, and in some cases initial application builds failed in environments where only the latest EAP jars were available in the maven repository. The EAP pom templates have been updated to eliminate confusion and application builds no longer fail.
errata-xmlrpc 2013-09-25 12:03:49 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-09-25 15:31:17 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-09-25 11:31:17 UTC
Dan McPherson 2017-03-08 17:35:18 UTC Target Release 1.2.3

Back to bug 1004868