Adam Murdoch wrote:
Steve Appling wrote:
Perhaps a simpler approach that would meet my needs would be to make
sure that the buildSrc project is built before settings.gradle is
executed and then have the buildSrc in the classpath for
settings.gradle. Is there a reason that settings.gradle is executed
before buildSrc is built?
This is a potential solution. One implication of building buildSrc
before evaluating the settings file is that you no longer have a place
where you can specify things about the buildSrc project (locations,
tasks to execute, configurations, etc).
I have made changes to build buildSrc first, then evaluate settings with
the buildSrc results in the classpath. This allows you to use classes
defined in buildSrc both in settings.gradle and in your build.gradles.
What do people think about this approach? Would a patch to do this be
well received?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
