JBDS 5 and JBDS 6 is not able to create (work with) EAP 6.1 server because of change in module structure (https://issues.jboss.org/browse/MODULES-154): https://issues.jboss.org/browse/JBIDE-13537 There exists a workaround, to make symlink from old location to location in the new structure, see https://community.jboss.org/message/796711?_sscc=t
We need to sync new JBDS 5/6 release with EAP 610 to provide appropriate support for developers for new EAP version. Adding qa_ack.
Rob Stryker <rob.stryker> made a comment on jira JBIDE-13537 Mock test and real test added. pushed to maintenance.
Rastislav Wagner <rawagner> updated the status of jira JBIDE-13537 to Closed
Rastislav Wagner <rawagner> made a comment on jira JBIDE-13537 verified in JBDS 6.0.1 v20130304-0526-B338
Rob Stryker <rob.stryker> updated the status of jira JBIDE-13537 to Reopened
Rob Stryker <rob.stryker> updated the status of jira JBIDE-13537 to Resolved
Martin Malina <mmalina> updated the status of jira JBIDE-13537 to Closed
Martin Malina <mmalina> made a comment on jira JBIDE-13537 Closing again.
Michelle Murray <mmurray> updated the status of jira JBIDE-13537 to Reopened
Michelle Murray <mmurray> made a comment on jira JBIDE-13537 Reopening to edit release notes text
Michelle Murray <mmurray> updated the status of jira JBIDE-13537 to Resolved
Michelle Murray <mmurray> made a comment on jira JBIDE-13537 Resetting resolution after reopening to edit release notes text
Rastislav Wagner <rawagner> made a comment on jira JBIDE-13537 closing.
Adding back the acks that were removed when I set component.
EAP 6.1 is compatible with JBDS 6.0.1 which is currently the latest released version
Think this should be closed.
It depends if we want to track that EAP 6.1 is no longer supported by older versions of JBDS than 6.0.1 (that means mainly by JBDS 5)