[
https://jira.jboss.org/jira/browse/JBIDE-4088?page=com.atlassian.jira.plu...
]
Denis Golovin commented on JBIDE-4088:
--------------------------------------
There is a preference item that indicates that, but it is saved in workspace, that's
why it is not working for old workspaces.
If user chooses existing workspace after install the runtimes are not
configured
--------------------------------------------------------------------------------
Key: JBIDE-4088
URL:
https://jira.jboss.org/jira/browse/JBIDE-4088
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: integration
Affects Versions: 3.0.0.GA
Reporter: Jim Tyrrell
Fix For: 3.1.0.M2
A couple of users had the problem they could not understand why the servers configured in
the installer were not available to them
after installing JBDS 2.
The problem was they selected an existing workspace which we don't mess with by
default.
I see two solutions/fixes for this:
1) Have a different default workspace name per major release (i.e. jbds2-ws)
Problem: users will bump into the same issue when they then install JBDS 2.0.1
2) Have the runtime configuration some how mark the workspace with that it have been
executed or not and then have some
ui in case there can be some conflicts between server names etc ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira