[
https://issues.jboss.org/browse/JBDS-3562?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-3562:
-----------------------------
Attachment: JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png
JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png
Len asked a question in email:
{quote}Question for everyone - What version string will be displayed in the
"about" dialog? If the version is 9.0, then the user will need some easy way to
identify the embedded EAP.{quote}
As expected, there's no way in JBDS to tell if you're using the patched EAP 6.4 or
the original. I launched both JBDS 9.0.0.GA_B124 (orig from October) and JBDS 9.0.0.GA_B12
(patched in Dec) against the same workspace, and here's what I see for available EAP
runtimes within JBDS:
!JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png!
!JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png
Note too that if you look in the version file for the patched EAP6.4, it says:
{code}
$➔ cat version.txt
Red Hat JBoss Enterprise Application Platform - Version 6.4.0.GA
{code}
So, once again, the only way to know you're using the patched EAP is to look for the
bugzilla number in the EAP install folder:
{code}
$➔ find . -iname "*1281963*" -o -iname "*bz*"
./modules/system/layers/base/.overlays/BZ1281963
./modules/system/layers/base/.overlays/BZ1281963/org/apache/commons/collections/main/commons-collections-3.2.1.redhat-3-bz-1281963.jar
./.installation/patches/eap-640-bz1281963
{code}
Prepare for 9.0.1 (9.0.0 with patched EAP 6.4.0 BZ1281963 /
CVE-2015-7501)
--------------------------------------------------------------------------
Key: JBDS-3562
URL:
https://issues.jboss.org/browse/JBDS-3562
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: build
Affects Versions: 9.0.1.GA
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 9.0.1.GA
Attachments: 900GAvs901GA_B6.p2diff.txt,
JBDS900GA-respin_diffs__EAP640-BZ1281963.png,
JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640.png,
JBDS900GA-respin_diffs__EAP640patched-looks-the-same-as-EAP640__002.png,
JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP.png,
JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_210_refs.png,
JBDS900GA-respin_diffs__google.gson_JBDSTPvsJBDSCentralTP_224_refs.png,
JBDS900GA-respin_diffs__o.e.jst.plugins.manifest.mf.png,
JBDS900GA-respin_diffs__p2director.manifest.mf.png,
JBDS900GA-respin_diffs__plugins_including_gson2.1.0vs.2.2.4.png,
JBDS900GA-respin_diffs__readme.txt.png
Tracker JIRA to house things to do to prepare for 9.0.1 / 9.1.0 branches & builds.
Because JBDS 9.0.0 includes the compromised version of
apache.commons.collections (JBDS-3560, JBDS-3561), we need to at some point respin it,
which
will include:
a) updated JBT/JBDS target platforms 4.50.1.* and 4.51.1.*
b) repin of JBDS update sites and installer jars
To that end, I've created the following new branches:
https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.1.x
https://github.com/jbosstools/jbosstools-target-platforms/commits/4.51.1.x
And I've bumped the version of the target platforms in the 4.50.x and
4.51.x branches to 4.50.2.Beta1-SNAPSHOT and 4.51.2.Beta1-SNAPSHOT,
respectively.
JBDS is now at version 9.1.0 in the 4.3.x branch and 9.0.1 in the
4.3.1.x branch.
https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3...
(new, 9.0.1)
https://github.com/jbdevstudio/jbdevstudio-product/commits/jbosstools-4.3.x
(updated to 9.1.0)
So, now we just need to ensure that the correct BUILD_ALIAS (CR1 for
9.0.1, Beta1 for 9.1.0) and target platforms are used.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)