[jbosstools-issues] [JBoss JIRA] (JBIDE-17152) Support multiple versions of jQuery in the jQuery Mobile Palette

[Konstantin Marmalyukov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-17152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Marmalyukov updated JBIDE-17152:
-------------------------------------------

    Component/s: jsp/jsf/xml/html source editing
                     (was: visual-page-editor-core)

    
> Support multiple versions of jQuery in the jQuery Mobile Palette
> ----------------------------------------------------------------
>
>                 Key: JBIDE-17152
>                 URL: https://issues.jboss.org/browse/JBIDE-17152
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: jsp/jsf/xml/html source editing
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Vineet Reynolds
>
> This to track JBDS-3016. Multiple versions of jQuery are expected to be supported.
> The palette currently includes 1.10.2, but users could expect multiple versions to be supported; jQM 1.4.2 supports jQuery Core 1.8 + and was tested on jQuery 2.0.3. Users not wanting to support MSIE 6-8 would already be on jQuery 2; this is especially true of Cordova.
> Thus, for a given version of jQueryMobile, at least two versions of jQuery can be recommended for use: a jQuery 1.x version and jQuery 2.x version. Generally, the [Travis build file|https://github.com/jquery/jquery-mobile/blob/1.4.2/.travis.yml] contains info on the versions tested for a jQM release (this is not wholly reliable, but is a good place to start).
> Note, in the near future (6-12 months), the following versions of jQuery are expected to be released:
> * 1.11.1 (might be released this week), 1.12 and probably 1.13
> * 2.1.1 (might be released this week), 2.2 and possibly 2.3.
> These may be tested to work with a version of jQueryMobile, at the point of a jQueryMobile release,

--
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