[
https://jira.jboss.org/browse/JBDS-1380?page=com.atlassian.jira.plugin.sy...
]
Denis Golovin resolved JBDS-1380.
---------------------------------
Resolution: Done
It works as expected and let create servers with unmatched type/version to handle some
cases we cannot cover, like let user to register new versions or AS or EAP Based
distributions that can be released after JBDS 4.0.0.GA is publically available.
Version list in installer contains versions that actually supported by runtime
configuration plugin. Problem here is that installer server configuration step and runtime
plug-in has different implementation for the same features and sometimes they get out of
sync.
I'm fixing this issue and opening new one to address problem explained above.
JBDS installer refers SOA-P 5.1 ER3 as invalid
----------------------------------------------
Key: JBDS-1380
URL:
https://jira.jboss.org/browse/JBDS-1380
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: installer
Affects Versions: 4.0.0.Beta2
Environment: JBDS 4.0.0.beta2 #123, Linux 64
Reporter: Jiri Peterka
Assignee: Denis Golovin
Fix For: 4.0.0.CR1
Attachments: invalid-soap-version.png
JBDS installed refers SOA-P 5.1 ER3 as invalid
Steps:
1. Run installer
2. On Select Platform and Servers wizard page click Add
3. Set location to SOA-P 5 ER 3
Invalid version is reported (see screenshot)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira