Hans, I think that this solution works, and gives me what I need for now. Longer-term, I think it would be ideal if Gradle supported something along the lines of what I can do in Maven:
+ Build project libraries + Build custom Gradle tasks/plugins that reference these libraries + Use the custom Gradle tasks/plugins above at build time in other projects (within the same multi-project build) + Expose the tasks/plugins to the outside world to be consumed by other projects' builds Again, what you have provided is great, and gives me what I need, but as I move beyond a unit test project to having multiple projects which need to use the Generator at build time, having to replicate this solution in each project is less than ideal. -- View this message in context: http://www.nabble.com/Advice-on-multi-project-build-source-setup-tp16960881p17105505.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
