[jbosstools-issues] [JBoss JIRA] (JBIDE-15614) Add support for EAP 6.2

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-15614:
-------------------------------------

I've merged in the current patches with only a slight change. 

It is not appropriate to add an eap6.2 server type until we discover incompatibilities that require it. So if we see anything that breaks,  management,  xpaths, server startup, publish, anything.  Until we see anything like that, we won't add a 6.2 server type.  Though we may wish to consider renaming the eap6.1 server and runtime types to 6.x (?)  If we feel confident there won't be any breakages, then we may consider doing that. 

[~maxandersen] - is renaming eap6.1 server nad runtime types to 6.x appropriate? We have an existing 6.0. 
                
> Add support for EAP 6.2
> -----------------------
>
>                 Key: JBIDE-15614
>                 URL: https://issues.jboss.org/browse/JBIDE-15614
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: runtime-detection, server
>    Affects Versions: 4.1.0.Final
>         Environment: JBDS 7.0.0.GA
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.1.1.Beta1
>
>
> 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
> 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
> Let me know if you want subtasks for these two.

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