]
Max Rydahl Andersen commented on JBDS-2481:
-------------------------------------------
[~ldimaggio] is this being requested to be released in 5.x stream ? users can use JBDS 6
or 7 now for this - or is this because SOA-P 5.2 tooling is not available on JBDS 6/7 yet
?
JBDS 5.0.0 and 5.0.2 is able to recognize EAP 5.2 runtimes - but does
not automatically create a corresponding server
---------------------------------------------------------------------------------------------------------------------
Key: JBDS-2481
URL:
https://issues.jboss.org/browse/JBDS-2481
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: runtime
Affects Versions: 5.0.0.GA, 5.0.2.GA
Environment: JBDS 5.0
JBDS 5.0.2
EAP 5.2
Reporter: Len DiMaggio
Assignee: Max Rydahl Andersen
Fix For: 5.x
Attachments: JBDS_50_GA.png, Screenshot-12.png, Screenshot-13.png,
Screenshot-14.png
If an EAP 5.2 server installation is referenced (Preferences->JBossTools Runtimes),
the runtime is correctly found by JBDS and listed as a runtime to be scanned at startup -
but - the corresponding EAP 5.2 server instance is not automatically created. The user
must create this server definition manually.
JBDS 5.0.0, and 5.0.2 is able to both create the runtime and automatically create
corrseponding servers for EAP 5.1 and EAP 6.0 - the issue seems to be limited to EAP 5.2
JBDS 6.0.0 is able to both create the runtime and automically create corrseponding
servers for EAP 5.1, EAP 5.2 and EAP 6.0
See attached screenshots.
(Thanks to Eric Schabell for finding this one!)
--
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: