[
https://issues.jboss.org/browse/JBIDE-13683?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-13683:
--------------------------------
Release Notes Text:
Cause: The direct cause of this issue is that runtime detection was not updated to
properly handle the second phase of instantiating the runtime into a server adapter.
Consequence: A JPP installation would be recognized by runtime detection, but would not
have a server adapter created for the user to make use of.
Fix: The complete fix is to update the server bean loaders to have a more specific
identification of jpp servers, as well as to update the runtime detection to ensure no
likely server types are ignored in the future
Result: A jpp installation will now be recognized AND instantiated into a proper server
adapter.
was:
Cause:
Consequence:
Fix:
Result:
JPP not instantiated by runtime detection
-----------------------------------------
Key: JBIDE-13683
URL:
https://issues.jboss.org/browse/JBIDE-13683
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.1.Final
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.1.Final, 4.1.0.Alpha2
Use runtime detection against a folder containing JPP 6, and try to have it create the
server. It does not create any server.
--
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