Hans Dockter wrote:
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).
This is a good plan.
Personally, I'd like to be able to download a small gradle distribution
which then downloads the bits I need, in slightly finer grained chunks
than the wrapper does (In fact, the solution could be to change the
wrapper so it can download stuff from an ivy repository).
In order to add things like reporting to the plugins, currently we have
to add jars to gradle's lib directory. I'm reluctant to keep just adding
jars here. Fetching them from a repository somewhere if I happen to use
the java plugin would be a much nicer situation.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
