[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3867) Duplicate EAP server runtime names.

[Aliaksey Nis (JIRA)]

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

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. 






> Duplicate EAP server runtime names.
> -----------------------------------
>
>                 Key: JBIDE-3867
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3867
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.GA
>         Environment: WindowsXP SP2
> JBoss Tools
> Version: 3.0.0.GA
> Build id: JBossTools-ALL-win32-3.0.0.GA-N200902250001-H1455
> JRE 1.5_08
>            Reporter: Aliaksey Nis
>            Assignee: Rob Stryker
>             Fix For: 3.0.0.GA, 3.1.0
>
>
> 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. 

-- 
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