[jbosstools-issues] [JBoss JIRA] (JBIDE-16758) Verify support for EAP 6.3 and future versions

Martin Malina (JIRA) issues at jboss.org
Thu Jul 3 03:22:24 EDT 2014


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

Martin Malina commented on JBIDE-16758:
---------------------------------------

It was verified with the latest at the time - not sure exactly. Perhaps ER5 or so. But the EAP QE team keeps smoke testing their ER builds and we keep an eye on it too. This JIRA was created as a reaction to EAP 6.3 not working just before JBDS 7.1.1 was released and me applying a simple fix, so I wanted to make sure it works properly in 4.2.x.

> Verify support for EAP 6.3 and future versions
> ----------------------------------------------
>
>                 Key: JBIDE-16758
>                 URL: https://issues.jboss.org/browse/JBIDE-16758
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: server
>    Affects Versions: 4.2.0.Alpha2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta1
>
>
> Please verify support for future versions of EAP / Wildfly.
> For 4.1.x I created this simple fix to make EAP 6.3 work properly:
> https://github.com/jbosstools/jbosstools-server/pull/206
> It was a clone of a previous simple fix to add EAP 6.2.
> I noticed that this issue does not apply to master - EAP 6.3 works there.
> But it would be desirable if there was a more permanent fix that ensures that should a new version appear (EAP 6.4), it will just work unless there are changes that need special treatment.
> Looking at the code it seems that indeed you now have some other mechanism. Can you confirm that?



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jbosstools-issues mailing list