|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)
- [JIRA] (JENKINS-14103) Grails 2.0.4 not... [email protected] (JIRA)

Bump.
I've noticed this historically as well. I've always had manual grails installs because whenever I upgrade Grails versions, the latest are always not listed. I in the process of moving to auto-scaling EC2 slaves and need this functionality. Please update this now, and make sure this is regularly updated.