[
https://issues.jboss.org/browse/JBIDE-8273?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8273.
--------------------------------
Fix Version/s: (was: 3.2.1)
Resolution: Duplicate Issue
Duplicate of JBIDE-3537, which, sadly, is an upstream bug that will most likely not be
fixed.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261306
Server runtime mishmash when renaming runtimes
----------------------------------------------
Key: JBIDE-8273
URL:
https://issues.jboss.org/browse/JBIDE-8273
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.2.0.CR1
Environment: JBDS 4.0.0.CR1 H100, Linux 64
Reporter: Jiri Peterka
Assignee: Rob Stryker
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
There are quire weird situation in related Server definition when renaming particular
runtimes.
Steps:
1. Open Server Definition
2. Try change related runtimes names
After renaming there there are 2 bad scenarios:
1. Runtime lost for the server or
2. Runtime is wrong
For better imagination what's happening see
http://www.screencast.com/t/SvMv8gkRw0v
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira