[ https://issues.jboss.org/browse/JBIDE-13209?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-13209: ------------------------------------------- Assignee: Brian Fitzpatrick (was: Rob Stryker) Nick - "fixing" it in AS tools has little to zero value since when ESB 4.13 comes out we got the same problem and the whole current need for knowing the diff between 4.10 and 4.11 is about xsd name differences. Brian - can't we fix ESB detection to not complain about the version number match *exactly* and as long as it is 4.x we just take the highest known version ? Yes - this won't make the wizard put in the latest greatest XSD but at least it will work for new version (assuming XSD are backwards compatible which I assume they are) and users can easily (just like they do today when updating) set the proper XSD if need be. Tom - do you see any problems of making the ESB tooling just assume ESB 4.11 schema/names are ok for any future ESB 4.x+ releases so we avoid this need for constant adding specific version numbers for every minor release ? (p.s. we can of course still go and add additional versions support when we are doing an esb tooling release but just trying to avoid *forcing* a release of esb tooling just to support a minor update) -- 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