Doesn't "project" reference the current project as well?
Op 18 jun 2009 om 20:35 heeft Steve Appling <[email protected]>
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 parameter. This makes both allprojects.each { closure } and
allprojects { closure } work more consistently.
Steve Appling wrote:
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 pass the configured object to the closure as a parameter. Then
you could do:
allprojects { nextProject->
// use nextProject
}
Does this seem like a good change to configure?
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
