[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4088) If user chooses existing workspace after install the runtimes are not configured

[Max Rydahl Andersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-4088:
---------------------------------------

              Summary: If user chooses existing workspace after install the runtimes are not configured  (was: Can workspace directories with existing projects not be opened if they do not have the right signature.)
          Component/s: integration
        Fix Version/s: 3.1.0.M2
    Affects Version/s: 3.0.0.GA
          Description: 
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 ?



Jim, I couldn't decipher your title - let me know if my bestguess translation worked  ? :)

> 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