filed: http://jira.codehaus.org/browse/GRADLE-527
I have now built my first ear with gradle 0.6.1! Still a lot to do in
updating all gradle files in all projects, but I can now use gradle again.
Are there any big breaking changes in the DSL in upcoming releases? I'm
trying to decide if I
Both Project.subprojects and Project.allprojects take a closure and use it to
configure the requested set of projects. Is there a good way to access the
project that is currently being configured from inside the closure?
The only way I saw to do this was to modify ConfigureUtil.configure to
I was a little premature with my question. I can reference the delegate to get
to this. It still seems more obvious to use a closure parameter. This makes
both allprojects.each { closure } and allprojects { closure } work more
consistently.
Steve Appling wrote:
Both Project.subprojects and
Doesn't project reference the current project as well?
Op 18 jun 2009 om 20:35 heeft Steve Appling sajaka...@appling.org
het volgende geschreven:\
I was a little premature with my question. I can reference the
delegate to get to this. It still seems more obvious to use a
closure
Not in a subprojects { } or allprojects { } closure. It's a bit confusing,
and I'm hoping to look into a solution at some point. But for now, it's not
so straight-forward.
On Thu, Jun 18, 2009 at 3:01 PM, Levi Hoogenberg
levihoogenb...@gmail.comwrote:
Doesn't project reference the current
Levi Hoogenberg wrote:
Are you sure? I'm fairly certain that I'm doing this (with a subprojects
closure) in a 0.6.1 build script.
Op 18 jun 2009 om 21:41 heeft John Murph jmurph@gmail.com
mailto:jmurph@gmail.com het volgende geschreven:\
Not in a subprojects { } or allprojects { }
