[jbosstools-issues] [JBoss JIRA] Closed: (JBDS-831) If user chooses existing workspace after install the runtimes are not configured
Jiri Peterka (JIRA)
jira-events at lists.jboss.org
Thu Sep 9 11:58:49 EDT 2010
[ https://jira.jboss.org/browse/JBDS-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiri Peterka closed JBDS-831.
-----------------------------
Verified in JBDS 4.0.0.v201009011720R-H437-M2, Linux 64. Situation is: servers from JBDS-installation are automatically added into new or existing workspace (merged with another servers pre-defined in workspace).
> If user chooses existing workspace after install the runtimes are not configured
> --------------------------------------------------------------------------------
>
> Key: JBDS-831
> URL: https://jira.jboss.org/browse/JBDS-831
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 3.0.0.M4
> Reporter: Jim Tyrrell
> Assignee: Jiri Peterka
> Fix For: 4.0.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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list