Hi,
I would like to share my ideas on the future modularization of Gradle
(if possible implemented for 1.0).
- A very small core jar which has only one dependency on slf4j. No
build-in tasks. Other projects can use this in an embedded way for
whatever reason they need an api for dependency based programming.
Jars with plugins and Tasks can be programatically added.
- A groovy decorated version of the core jar, with the same use case
as above but more convenient to use if people want to pay the
dependency and performance penalty.
- A very small Java only stand alone version of Gradle. It has
folders where you can just place build script engines and plugin jars
which are then automatically picked up.
- A Groovy and Java build script engine (with an own Java Ant Builder).
In the best of worlds our standard Java tasks would have no
dependency on Ant. That would make embedding Gradle more convenient.
On the other hand delegating to Ant tasks saves a lot of work.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
