[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-1658) SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606550#comment-12606550 ] 

Martin Malina commented on JBDS-1658:
-------------------------------------

If you use the runtime detection in jbds preferences, it works fine. The problem only occurs if you add the server location during installation.

> SOA-P 4.3.0 standalone is not properly added to Server Runtimes after installation.
> -----------------------------------------------------------------------------------
>
>                 Key: JBDS-1658
>                 URL: https://issues.jboss.org/browse/JBDS-1658
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: runtime
>    Affects Versions: 4.1.0.M1
>         Environment: jbdevstudio-product-linux-gtk-4.1.0.v201105091943R-H400-M1, linux 32bit, Java Sun JDK 1.6_25
>            Reporter: Vlado Pakan
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 4.1.0.CR1
>
>         Attachments: editServerRuntimeEnvironmentDialogWarning.png
>
>
> When searching for runtimes select directory with SOA-P 4.3.0 standalone runtime. It's recognized as AS v.4.3.0 and added to available runtimes during installation. But after installation is finished and JBDS is run this runtime is defined as v. 4.2 runtime and therefore there is a warning displayed in Edit Server Runtime Environment dialog.
> When added manually via Preferences > Server Runtime > Environments > Add it's possible to add this runtime as JBoss EAP 4.3 runtime without warning displayed in Edit Server Runtime Environment dialog.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira