[
https://jira.jboss.org/jira/browse/JBDS-827?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBDS-827:
------------------------------------------
checked and in latest JBDS 2.0 the versions are as follows:
1.2.1.EAP_4.3_CP03
2.0.2-FP
hurray for inconsistency ;(
So it looks like the "AP" is our fault, and the EAP_4.3/EAP5/FP is the runtime
names.
We are kinda screwed - no combination will really work well - it will break project
examples that assumes .AP.
Here is what I suggest:
Keep the behavior as is for JBDS 2.0.x and JBDS 2.1.x and then in JBDS 3 we will use the
*exact* same naming scheme in autodetection as we do in the installer setup - that should
result in least amount of changes.
Do you agree?
Seam runtime should be 2.2.0.EAP, not 2.2.0.AP
----------------------------------------------
Key: JBDS-827
URL:
https://jira.jboss.org/jira/browse/JBDS-827
Project: JBoss Developer Studio
Issue Type: Bug
Components: seam
Affects Versions: 2.1.0
Reporter: Ondrej Skutka
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 2.1.0
There's a typo in Seam runtime label. It should be 2.2.0.EAP, not 2.2.0.AP
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira