- Previous thread: grails-user - groovy help fails on fresh install grails 1.3.3
- Next thread: grails-user - Wrap join table into domain object
- Threads sorted by date: grails 201007
On one of my projects I'm still using grails 1.1 and need to upgrade to the
latest jQuery but I see that the jQuery plugin now requires 1.2.2. Scanning
the mailing list and the JIRA tickets I don't see a reason why this was
updated (except for the fix from requiring 1.3.1 back down to 1.2.2). I'm
curious if there is a reason why the plugin now requires 1.2.2 or if it was
just set to that because Burt B asked? I don't mind branching the plugin and
updating it for my own purposes, but I thought I would check to see if there
was a reason I shouldn't be doing that in grails 1.1.
Thanks,
- Justin
On one of my projects I'm still using grails 1.1 and need to upgrade to the latest jQuery but I see that the jQuery plugin now requires 1.2.2. Scanning the mailing list and the JIRA tickets I don't see a reason why this was updated (except for the fix from requiring 1.3.1 back down to 1.2.2). I'm curious if there is a reason why the plugin now requires 1.2.2 or if it was just set to that because Burt B asked? I don't mind branching the plugin and updating it for my own purposes, but I thought I would check to see if there was a reason I shouldn't be doing that in grails 1.1.
Thanks,- Justin
latest jQuery but I see that the jQuery plugin now requires 1.2.2. Scanning
the mailing list and the JIRA tickets I don't see a reason why this was
updated (except for the fix from requiring 1.3.1 back down to 1.2.2). I'm
curious if there is a reason why the plugin now requires 1.2.2 or if it was
just set to that because Burt B asked? I don't mind branching the plugin and
updating it for my own purposes, but I thought I would check to see if there
was a reason I shouldn't be doing that in grails 1.1.
Thanks,
- Justin
On one of my projects I'm still using grails 1.1 and need to upgrade to the latest jQuery but I see that the jQuery plugin now requires 1.2.2. Scanning the mailing list and the JIRA tickets I don't see a reason why this was updated (except for the fix from requiring 1.3.1 back down to 1.2.2). I'm curious if there is a reason why the plugin now requires 1.2.2 or if it was just set to that because Burt B asked? I don't mind branching the plugin and updating it for my own purposes, but I thought I would check to see if there was a reason I shouldn't be doing that in grails 1.1.
Thanks,- Justin
I did this. Purely because I don't touch pre-1.2.2 releases now.
However there *were* problems around 1.1 era with including resources from plugins (pluginContextPath issues) which may preclude you using the new jq:resources mechanism that pulls jq in from the plugin instead of downloading it and installing it into your app. This approach is IMO much preferred because installing version X of jq will give you that version of jquery, with no need to mess with your project files.
This becomes more important when you factor in other grails plugins depending on certain versions of jquery (plugin). Grails would install the new jquery plugin they depend on, but you would then have multiple copies of jquery in your app (one in your web-app folder, one in the jquery plugin) and plugins might use one, your app the other etc.
Its just messy :)
Marc
~ ~ ~
Marc Palmer
Blog Twitter Grails Rocks
http://xircles.codehaus.org/manage-email
Related Threads
- Automação de Usinas de Alcool - debian
- Music/Audio CDROMs, DVDs, & Etch kernel Security Update. - debian
- gdm themes - how? - fedora
- Best way to back up mysql database - freebsd
- ACATS Target Requirement Question - gcc
- long select query result as as query string on another select statment - mysql
- [PHP] Encrypt database table - php
- A bit weird dictionary behavior - python