Hi Allan,
the current plugin system in Gradle is very basic. We are well aware
of this and it is clear that is has to evolve.
On May 7, 2008, at 3:54 PM, Allan Lewis wrote:
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.
No question about this.
Hopefully there will be a 0.2 release in June which will accommodate
the features you have proposed above.
I will also contact you during the implementation phase of those
features, to ask for feedback, if this is OK.
- Hans
--
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
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
