[forge-issues] [JBoss JIRA] (FORGEPLUGINS-158) Upgrade jQuery to 2.x

[Vineet Reynolds (JIRA)]

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

Vineet Reynolds moved WFK2-372 to FORGEPLUGINS-158:
---------------------------------------------------

           Project: Forge Plugins  (was: JBoss WFK 2)
               Key: FORGEPLUGINS-158  (was: WFK2-372)
        Issue Type: Task  (was: Requirement)
          Workflow: GIT Pull Request workflow   (was: CDW v1)
       Component/s: AngularJS Scaffold
                        (was: JavaScript Libraries)
          Security:     (was: JBoss Internal)
    Target Release:   (was: 2.5.0.GA)

    
> Upgrade jQuery to 2.x
> ---------------------
>
>                 Key: FORGEPLUGINS-158
>                 URL: https://issues.jboss.org/browse/FORGEPLUGINS-158
>             Project: Forge Plugins
>          Issue Type: Task
>          Components: AngularJS Scaffold
>            Reporter: Vineet Reynolds
>            Assignee: Vineet Reynolds
>
> Going by the [jQuery 2.0 release notes|http://blog.jquery.com/2013/04/18/jquery-2-0-released/], we should aim to use jQuery 2.x for several types of environments, due to the lack of support available for the 1.x baseline. PhoneGap/Cordova apps would be of concern to us.
> This would deprecate jQuery 1.x usage in the quickstarts. For now. the plan is to continue using jQuery 1.x in non-Cordova quickstarts and examples. Sites and apps are still expected to use jQuery 1.x since it carries IE6+ support.
> Upgrading jQuery usage in TicketMonster might prove to be a more complicated affair since it would require the Cordova dependent bits to run with jQuery 2.x, but also require the other bits (the desktop and mobile browsers based components) to use jQuery 1.x.

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