atom feed11 messages in org.codehaus.grails.devRe: [grails-dev] Plugins and 1.3
FromSent OnAttachments
Marc PalmerMar 30, 2010 3:15 am 
Graeme RocherMar 30, 2010 5:52 am 
Nicolas LupienMar 30, 2010 4:31 pm 
Peter LedbrookMar 30, 2010 11:22 pm 
Graeme RocherMar 31, 2010 12:29 am 
Mihai CazacuMar 31, 2010 1:23 am 
Marc PalmerMar 31, 2010 3:02 am 
Graeme RocherMar 31, 2010 3:37 am 
Peter BellMar 31, 2010 9:16 pm 
Graeme RocherApr 1, 2010 2:18 am 
Erik PragtApr 1, 2010 4:15 am 
Subject:Re: [grails-dev] Plugins and 1.3
From:Graeme Rocher (groc@vmware.com)
Date:Apr 1, 2010 2:18:05 am
List:org.codehaus.grails.dev

Yes its necessary since we have moved to using Ivy to resolve Grails plugins you have to define grailsCentral() as a repository. This is also important for folks who want to disable remote resolution (by removing grailsCentral())

Cheers

On Thu, Apr 1, 2010 at 6:16 AM, Peter Bell <lis@pbell.com> wrote:

I just upgraded an existing Grails 1.2.2 project (created under 1.2.1 originally) to the 1.3 RC. When I tried to run the app, it was unable to resolve the plugins (richui and searchable). I ended up adding grailsCentral() to the list of repos in my project BuildConfig.groovy. Some questions/comments: (a) Was that necessary or was I missing something ? (b) It looks like I have a grailsPlugins() and grailsHome() in the list of repos - do I still need those? (c) If this *is* a necessary step, might be worth noting this in the release notes (http://www.grails.org/1.3-M1+Release+Notes) (that it is a required step if you have plugins - not that it's an available option which is how I - perhaps mis - read it) Thanks! Peter