On 12/12/09 7:27 AM, Paul Speed wrote:
Adam Murdoch wrote:
On 12/12/09 7:16 AM, Paul Speed wrote:
I will try a later snapshot later today but note that the issue is
somewhat different than what is mentioned in GRADLE-708.
subprojects {
println( project.name );
}
Works for me even on 11/26's build but:
subprojects.each {
println( project.name );
}
each() is a Groovy method. There's not much we can do to change how
it behaves.
Honestly, that's what I figured. :)
Question: is there any advantage to using that over just subprojects
{}? Or am I just making my life harder?
I can't think of any advantage.
And a more related question, does the bug fix resolve things like:
configure(subprojects.findAll { it.path.lastIndexOf(':') == 0 }) {
println( project.name );
}
This should be fixed too.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
