[jbosstools-issues] [JBoss JIRA] (JBIDE-13992) Run On Server > Manually Define > EAP 6.0 > Server name defaults to "JBoss EAP 7.1 Runtime Server"

Nick Boldt (JIRA) jira-events at lists.jboss.org
Thu Apr 11 13:26:17 EDT 2013


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

Nick Boldt commented on JBIDE-13992:
------------------------------------

This appears to go away when I update to Alpha2 from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/


                
> Run On Server > Manually Define > EAP 6.0 > Server name defaults to "JBoss EAP 7.1 Runtime Server"
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13992
>                 URL: https://issues.jboss.org/browse/JBIDE-13992
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Rob Stryker
>         Attachments: installed-features.png, installed-jbt-4.1Alpha1-plugins.png, JBEAP6.0_is_JBEAP7.1.png
>
>
> Testing out some BPEL examples (JBTIS-62).
> Installed Eclipse Kepler M6 JEE.
> Installed BPEL features. Got a pile of JBT 4.1.0.Alpha1 dependencies along for the ride.
> Run On Server > Manually Define > EAP 6.0 > Server name defaults to "JBoss EAP 7.1 Runtime Server".
> Shouldn't that be EAP 6.0, not 7.1?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list