[
https://issues.jboss.org/browse/JBIDE-10244?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-10244:
---------------------------------------
Another thing, this problem is only reproducible if you really use a new workspace. So let
me describe the steps again:
1. Add several paths in JBoss Tools Runtime Detection and "Every time" for at
least one of them
2. Restart Eclipse with a new workspace
3. When asked about adding the found runtimes, press Cancel
4. See the added runtimes in Preferences -> Server -> Runtime Environments - FAIL
Note that once I restart Eclipse with the same workspace again it doesn't happen. So
this only happens when you have a new workspace.
Cleaning up Runtime plugin
--------------------------
Key: JBIDE-10244
URL:
https://issues.jboss.org/browse/JBIDE-10244
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime detection
Affects Versions: 3.3.0.M4
Reporter: Snjezana Peco
Assignee: Max Rydahl Andersen
Fix For: 3.3.0.Beta1
Attachments: jbide-10244.patch
The Runtime detection has changed the way runtimes are detected when starting JBDS/JBT.
The runtime plugin contains some deprecated stuff that needs to be removed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira