As JQM and JQ are included via a Wookie feature it is not possible for the widget to determine the version of them being used. This will lead to deployment problems when a feature of a newer version is not available in the wookie server in use.
This is not just hyperthetical as I just hit a problem with the JQM $.mobile.path.parseUrlfunction being available in trunk but not on a test server.
I propose the feature use have specify a version (at least for JQM). If none is specified us the latest
I'd prefer to directly include JQM from the widget source. As it is we now have a tighter dependency on the Wookie server version - if a new JQM is released all target Wookie servers must be updated if the widget is to use it.