Bug 245246 - Some RHEL5 Base packages need upgrading
Summary: Some RHEL5 Base packages need upgrading
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: JBoss Enterprise Application Platform 4
Classification: JBoss
Component: distribution
Version: 4.2.0
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Vinu S Renish
QA Contact: Len DiMaggio
URL:
Whiteboard:
Depends On: 245226 245229 245231 245233
Blocks: 251533 251537
TreeView+ depends on / blocked
 
Reported: 2007-06-21 21:03 UTC by Fernando Nasser
Modified: 2008-02-08 13:56 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-02-08 13:56:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Fernando Nasser 2007-06-21 21:03:00 UTC
JBoss AS EAP 4.2 requires some packages at newer versions than the ones that
come in the RHEL5 Base, so these need to be upgraded.  It must be thougly tested
if the upgrades cause any problems for existing RHEL-5 applications, like
Tomcat5 (and indirectly Eclipse) and others.

Bugs have been filed for individual component upgrades.

Comment 1 Michael Hideo 2008-01-17 05:50:26 UTC
Vinu,

Please move to JIRA if necessary.

Comment 2 Fernando Nasser 2008-02-08 13:56:39 UTC
This is actually an aggregator, or tracking, bug against the Red Hat Enterprise
Linux (RHEL) distribution regarding the Java packages in "base" (see list of
dependencies).  For RHEL-5 itself it is being tracked in the Bug #250670.

The packages in RHEL-5 are compiled with GCJ, however, so we end up using EAP
own builds of the packages, even if at the right version, and made file copies
(instead of links) of them to avoid false-positives in the signature
compatibility  tests performed by QE.  This situation can be revisited if
IcedTea replaces GCJ in a future RHEL-5 update.

Nevertheless, the base packages should be updated, as that facilitates people
that want to use the RPMs for community version of JBoss (from jpackage.org) on
RHEL-5.  But that is tracked on the Bug #250670, so I am marking this one, which
is for EAP, as DEFERRED.

No need to create a JIRA for it.


Note You need to log in before you can comment on or make changes to this bug.