Bug 960979 - Upgrading to EAP 6.1 breaks tomcat6 from the EWS 1.0 channel
Summary: Upgrading to EAP 6.1 breaks tomcat6 from the EWS 1.0 channel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: distribution
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-08 12:44 UTC by Brenton Leanhardt
Modified: 2019-03-01 12:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-01 12:29:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Brenton Leanhardt 2013-05-08 12:44:54 UTC 
Description of problem:
This is related to Bug #959993.  I'm not sure what component this should be filed against.  This bug likely only exists in the RPM distribution of EAP 6.1 and EWS 1.0.

Currently OpenShift Enterprise only support the jboss EWS 1.0 cartridge.  We previously instructed customers to use the EWS 1.0 RHN channel.  However we found that when upgrading the JBoss EAP cartridge to use the 6.1 content the EWS 1.0 cartridge would no longer be able to compile JSPs.

The workaround for OpenShift Enterprise is simply to have customers use the EWS 2.0 content sets for the EWS 1.0 cartridge as that does work as expected.  I'm filing this bug simply so that others can be aware in case they are affected.

If there are supported combinations of JBoss RHN channels it would be helpful for us to know.  Right now we are operating on the assumption that we will be able to have the EWS 2.0 content sets and the EAP 6 content sets enabled on the same machine.
Note You need to log in before you can comment on or make changes to this bug.