[ https://jira.jboss.org/jira/browse/JBIDE-3867?page=com.atlassian.jira.plu... ] Aliaksey Nis updated JBIDE-3867: -------------------------------- Priority: Major (was: Minor) -- 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-3867?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3867: ------------------------------------ I am not experiencing this part. After creating the first runtime / server combination (where the runtime name is EAP runtime), the second pass through the default runtime name is "JBoss EAP 4.3 Runtime". As far as I remember, my wizard *never* caches previous values nor does wtp. I'm thinking of adding in caching for the most recent home directory, to be quicker, but as of now nothing is cached that I can see. -- 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-3867?page=com.atlassian.jira.plu... ] Aliaksey Nis updated JBIDE-3867: -------------------------------- Description: Pepare two installations of JBoss EAP server. EXECUTE: Main menu > Window > Preferences > Server > Installed runtimes. Press Add. EXECUTE: Select EAP 4.3 type. Enable Server checkbox. Press Next. EXECUTE: Select path to server installation1, runtime name left unchanged ("JBoss EAP 4.3 Runtime"). Press Finish. EXECUTE: Main menu > Window > Preferences > Server > Installed runtimes. Press Add. EXECUTE: Select EAP 4.3 type. Enable Server checkbox. Press Next. EXECUTE: Select path to server installation2. Name of runtime - left unchanged (default "JBoss EAP 4.3 Runtime" ). FAILURE: No sights of warning about existing runtime with same name. For example - in JBoss 4.2 server runtime selection wizard automatically add (2) to runtime name and check possible duplicate names. EXECUTE: Press Next. Press Finish. ASSERT: New server with name " ... (1)" appears in server list. FAILURE: Newly created runtime - didn't appear in runtimes list. Newly created server points to runtime from server installation1 instead of installation2. was: Pepare two installations of JBoss EAP server. EXECUTE: Main menu > Window > Preferences > Server > Installed runtimes. Press Add. EXECUTE: Select EAP 4.3 type. Enable Server checkbox. Press Next. EXECUTE: Select path to server installation1, change input name - "EAP runtime". Press Finish. EXECUTE: Main menu > Window > Preferences > Server > Installed runtimes. Press Add. EXECUTE: Select EAP 4.3 type. Enable Server checkbox. Press Next. EXECUTE: Select path to server installation2. Name of runtime - left unchanged ("EAP runtime" - cached name from previous runtime creation). FAILURE: No sights of warning about existing runtime with same name. For example - in JBoss 4.2 server runtime selection wizard automatically add (2) to runtime name and check possible duplicate names. EXECUTE: Press Next. Press Finish. ASSERT: New server with name " ... (2)" appears in server list. FAILURE: Newly created runtime - didn't appear in runtimes list. Newly created server points to runtime from server installation1 instead of installation2. -- 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-3867?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3867: ------------------------------------ committed this to 3.0.x branch also as I think this is a really annoying bug and would slow people down. -- 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