[jbosstools-issues] [JBoss JIRA] (JBIDE-10244) Cleaning up Runtime plugin
[
https://issues.jboss.org/browse/JBIDE-10244?page=com.atlassian.jira.plugi...
]
Snjezana Peco resolved JBIDE-10244.
-----------------------------------
Resolution: Done
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
Not sure what you mean by FAIL here. I have tried to reproduce the issue. When pressing
Cancel, runtimes aren't added either in the new or in the old workspace.
This is the expected behavior.
IMO should have test for this not breaking in trunk
Will try to find a way to test this case. JUnit tests start using a new configuration and
workspace. We have to start Eclipse when some runtime paths already exist.
Committed to the 3.3.0.Beta1 branch too.
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