[
https://issues.jboss.org/browse/JBIDE-15765?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15765:
-------------------------------------
I would like to note the following. While ER-3 has only 1 match for
JBoss-Product-Release-Name on a search through the entire modules directory, ga has 2.
such matches. And they conflict.
[rob@rawbdor modules]$ grep -R "JBoss-Product-Release-Name" *
system/layers/base/org/jboss/as/product/eap/dir/META-INF/MANIFEST.MF:JBoss-Product-Release-Name:
EAP
system/layers/gatein/org/jboss/as/product/jpp/dir/META-INF/MANIFEST.MF:JBoss-Product-Release-Name:
Portal Platform
The first match is incorrect. The second match seems correct, but it is in a location that
violates the spec we were told would be honored. The correct match seems to live in
system/layers/{LAYER}/org/jboss/as/product/{SLOT}/dir/META-INF/MANIFEST.MF.
JPP 6.1 recognized as AS 7.2
----------------------------
Key: JBIDE-15765
URL:
https://issues.jboss.org/browse/JBIDE-15765
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.1.1.Beta1
Reporter: Radoslav RĂ¡bara
Assignee: Rob Stryker
Priority: Critical
Labels: respin-a
Fix For: 4.1.1.Beta1
Attachments: jpp 6.1 recognized as AS 72.jpg
JBoss Portal 6.1.0 Final is recognized as AS 7.2 in JBoss Runtime Detection (Type: AS,
Version: 7.2). However, JPP 6.1.0 Beta is recognized correctly as JPP 6.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira