[ 
https://issues.apache.org/jira/browse/WOOKIE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120797#comment-13120797
 ] 

Scott Wilson commented on WOOKIE-241:
-------------------------------------

The feature is really a convenience for developing widgets for Wookie; you're 
correct Steve that for portability across environments you would include the 
JQM scripts directly.

We could add a version id to the feature name e.g. 
"http://jquerymobile.com/1.0";; the feature spec itself in W3C doesn't permit 
version attributes.

I think it only makes sense to do this for stable versions of JQM (1.0,1.1) 
though rather than alpha/beta/RC versions.
                
> Version problems with JQueryMobile feature
> ------------------------------------------
>
>                 Key: WOOKIE-241
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-241
>             Project: Wookie
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.9.0
>         Environment: Any widget using the JQueryMobile feature
>            Reporter: Steve Lee
>             Fix For: 0.9.2
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to