> it does not solve the ESB plugin side which still would have to re-released just to support a new updated esb plugin afaics.

From what I can see, internal changes to the structure of the esb would require a re-release anyway. IT seems different logic needs to be done for each release to even determine the version fo the release (strange i admit. That's a problem with the esb runtime of course). But as long as that's changing, then a re-release is pretty much 100% required anyway.

Need to add ESB 4.12 option with constraints -------------------------------------------- Key: JBIDE-13209 URL: https://issues.jboss.org/browse/JBIDE-13209 Project: Tools (JBoss Tools) Issue Type: Task Components: esb Reporter: Tom Cunningham Assignee: Brian Fitzpatrick Fix For: 3.3.2, 4.1.0.Alpha1, 4.0.x Attachments: JBIDE-13209.patch SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions. Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether.