[ https://jira.jboss.org/jira/browse/JBIDE-4088?page=com.atlassian.jira.plu... ] 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 ? :) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4088?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-4088: --------------------------------- Fix Version/s: 3.1.0.M3 (was: 3.1.0.M2) it could be fixed by adding version of JBT where runtimes were initialized. so first start in new version should be able to understand there is new installation used on old workspace and after that we have to find way to deal with conflicts between server names. -- 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

[ https://jira.jboss.org/jira/browse/JBDS-831?page=com.atlassian.jira.plugi... ] Jim Tyrrell commented on JBDS-831: ---------------------------------- I think you got it, the problem as I saw this was if I have an existing workspace say against the JBDS 2.0 and targeting EAP 4.3. If I am not careful when I run and install JBDS 2.1 against EAP 5.0 I might have some big problems in my project. There were some very odd behavior, and it is not exactly clear to me how I would import/modify the old workspace to work in the new JBDS 2.1 with EAP 5.0. -- 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

[ https://jira.jboss.org/jira/browse/JBDS-831?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBDS-831: ------------------------------------- Component/s: installer (was: integration) (was: runtime) Assignee: Denis Golovin Jim, "import" is done by just using the old workspace location when asked for it. No specific import needed, just be aware that you might have issues going back to JBDS 2.x with the same workspace. -- 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

[ https://jira.jboss.org/jira/browse/JBDS-831?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBDS-831: ------------------------------- Fix Version/s: 3.1.0.beta1 (was: 3.0.1.GA) Moving to next version, because to fix it properly there are to many things to do like: - Distinguish old workspace from previous version - migrate current projects to new runtimes - verify runtimes from previous version - interact with user to select preferable options (tentative) -- 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

[ https://jira.jboss.org/browse/JBDS-831?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen commented on JBDS-831: ------------------------------------------ Snjezana, this is related to runtime detection setup. Not sure if we can handle this well; please comment when you have you looked at the current runtime detection support. -- 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

[ https://jira.jboss.org/browse/JBDS-831?page=com.atlassian.jira.plugin.sys... ] Snjezana Peco resolved JBDS-831. -------------------------------- Resolution: Done Now JBoss runtimes will be initialized after every installation of JBDS, once for every workspace (a new or an old workspace). -- 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

[ https://jira.jboss.org/browse/JBDS-831?page=com.atlassian.jira.plugin.sys... ] 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). -- 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