Hi Spencer, I am not happy with this approach too. Something like "leaveprojects" would be cool. A while ago, there was another thread here on the list about identifying leaveprojects, but I can't remember and didn't found a link. Personally we never had a reason to nest my projects in that manner. We transform our nested repository structure to a two level root/child approach by redefining the projectPath in the settings.gradle
regards, René > --- On Wed, 9/14/11, Rene Groeschke <[email protected]> wrote: > <snip> To avoid applying plugins to the dao project you can rewrite your > subprojects closure to add an additional check that root projects don't > apply any plugins and settings: > ---------- > subprojects { > if(!subprojects){ > > apply plugin: 'java' > Now there's an interesting pattern that really makes you look twice to > figure out exactly what is going on with the groovy code there. > > It should be fairly easy to simply define a standard "leafprojects" build > script block, just like "allprojects", and "subprojects" -- it is a DAG of > projects after all. > > -Spencer --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
