[
https://issues.jboss.org/browse/JBIDE-10244?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-10244:
---------------------------------------
Snjezana, OK, I cannot reproduce this now. But I suspect that when I saw this problem it
was related to JBDS-2048 - because the paths added during installation weren't added
properly, so I could add them again. And then in a new workspace even if I clicked Cancel
to the offered runtimes, they were added anyway (because it was the same runtimes that I
added during installation). Anyway, I'll recheck this in a new build with JBDS-2048
fixed.
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: Snjezana Peco
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