Hans Dockter wrote: > > Excellent. That's a long awaited feature. Quite a few users have asked for > that during the last year. > > @Helmut: We are finally there :). It would be great if you could try it > out. > > - Hans >
hi hans, i have done so and it works for me .. though i am not sure, i will use it, as atm. i have been fallen back to simply file-copy the war to repository-dir(s) and use no automated multi-build for grails-projects ... -> keep things simple. todays grails-app-build is complicate and heterogeneous and it tends to get even more complicate using the gradle-wrapper. i think, peter ledbrook is right when he states, that a deeper integration of gradle is needed to get a real smart and sustainable build for grails-apps: "It doesn’t make sense for Grails developers to spend a lot of their time on build stuff when another tool is now available that will do most of the work itself. The build system also doesn’t play particularly well with other build tools, which can make adoption in the enterprise rather tricky. And a clean room implementation means clearing out a lot of cruft and being able to resolve some outstanding and difficult problems." -> http://www.cacoethes.co.uk/blog/groovyandgrails/grails-2-0-1-gradle-for-the-win it will be quite a challenge to successfully realize this for grails-2. gradle would surely benefit from this too. gruesse -- View this message in context: http://old.nabble.com/Build-Grails-projects-with-Gradle-tp27471143p27652569.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
