Comments on: Building a Grails project with Gradle

By: Peter

Peter — Fri, 27 Aug 2010 06:33:05 +0000

Yes, I was going to refer you to that page Luke Daley has been doing some more work on the plugin, so might see a version 1.1 shortly. That reminds me, I need to revert the README back to version 1.0.

By: James Higgins-Thomas

James Higgins-Thomas — Thu, 26 Aug 2010 22:05:37 +0000

Or, better, refer to here: http://github.com/grails/grails-gradle-plugin for more current information

By: James Higgins-Thomas

James Higgins-Thomas — Thu, 26 Aug 2010 21:39:14 +0000

Ah, to that last point – add
mavenRepo urls: ‘http://repository.jboss.org/nexus/content/groups/public-jboss/’
to the second repositories {} collection…

By: James Higgins-Thomas

James Higgins-Thomas — Thu, 26 Aug 2010 21:31:49 +0000

Many thanks for doing this! I’ve struggled trying to integrate a grails sub-component with non-grails projects before and this looks like it’s super simple. Haven’t gotten it working yet (I think my mind refuses to wrap around the maven/ivy dependency models). I am using Grails 1.3.4 and had to make two changes (so far):

apply id: “grails” -> apply plugin: “grails” {as noted in the above thread}

and

compile “org.grails:grails-crud:1.2.0″, “org.grails:grails-gorm:1.2.0″ -> compile “org.grails:grails-crud:1.3.4″, “org.grails:grails-gorm:1.3.4″

Now if I can just figure out the reference to org.jboss.netty#netty;3.1.5.GA …

By: John Stoneham

John Stoneham — Tue, 20 Jul 2010 23:43:27 +0000

Notes for those finding this blog post: trying this with gradle 0.9-preview-3 and the latest snapshot, I have to change the second script above to say

apply plugin: “grails”

By: Peter

Peter — Tue, 08 Jun 2010 16:58:27 +0000

Hmmm…something else I need to take a look at. Too much to do! What error do you get if you don’t apply the java and Groovy plugins? It delegates to the Grails build, so those plugins shouldn’t be needed.

By: Fred Grott

Fred Grott — Tue, 08 Jun 2010 16:51:47 +0000

Peter, I have not completed full testing yet but I have found with gradle 0.9 preview 3 that I had to apply plugins java and groovy before the grails plugin..

No task with same name conflicts so far

By: Peter

Peter — Thu, 06 May 2010 09:27:06 +0000

OK, I’ve released a new 1.0-SNAPSHOT. If there aren’t any reports within a couple of weeks, I’ll release as 1.0.

By: Peter

Peter — Tue, 04 May 2010 08:18:20 +0000

@Helmut Thanks for the report. I have Ben’s changes incorporated locally now, but I still need to resolve this “task with that name already exists” error. Hopefully one of the Gradle team will be able to help out. Once that’s fixed, I’ll re-release the plugin, probably as version 1.0.

By: Helmut Tammen

Helmut Tammen — Sun, 02 May 2010 09:59:39 +0000

I detected another issue that only appears when using the Grails plugin (does not appear with Groovy or Java plugin).

When defining a new task in the build script like
task doit << {
println "ready"
}

I get the following runtime error:
Cause: Cannot add task ':doit' as a task with that name already exists.

If I use this it works:
task doit(overwrite: true) << {
println "ready"
}