[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-17032: ----------------------------------------- I think hardcoding versions is safe, for the default versions. But, if we can fetch info about new version releases, that would be good if we can get it right. Getting the latest version of jQuery Core correctly would be important. For minor version updates to jQM, I've noted that the team does not change the major version numbers for jQuery support; patch updates to jQuery are accepted. So, hypothetically, in the future, jQueryMobile 1.4.3 will work against jQuery 1.8 - 1.10.3 / 2.0.4 (where all three - jQM 1.4.3, and jQ 1.10.3 / 2.0.4 are unreleased at the moment), because jQM 1.4 was tested on jQuery 1.8-1.10/2.0). A pattern search for 1.4.* and 2.0.* would therefore be fine for now. But it would be even better if we can store this info on a server, have JBDS access it and update itself correctly. We can therefore control what versions are supported in JBDS; I know it is fairly impossible that a minor or patch update should break JBDS, so treat this as a conservative answer. And yes, it is better to use the latest versions unless the user changes his choice. -- This message was sent by Atlassian JIRA (v6.2.3#6260)