Hello,
let me first confess, that I love the gradle way, its flexibility and its ease
of usage. But what I can't accept is the duration of a gradle build.
When I startet with gradle, I had a project consisting of 25 subprojects,
which I wanted to split into 3 top-level projects. I created the new
directory structure and mounted the subprojects to the new location (with
bind option).
Than I worked out the gradle scripts for those 3 toplevel projects with their
corresponding supprojects.
The timings are taken from a gradle-build with tasks "clean, assemble and
upload". All gradle scripts are unchanged, so no script compilation needed.
The ant timing include the unit tests of every subproject as well, which I did
not implement with gradle yet and ant creates 2 installers, whereas gradle
creates only one.
The timings are:
ant: complete 0:35 min (35 seconds)
gradle: Prj-1 0:20 min (6 subprojects)
Prj-2 0:25 min (1 subproject)
Prj-3 5:10 min (18 subprojects)
Before I started measuring the times, I guessed that gradle takes more than 10
times the time of ant, but reality is even harder ...
So I'm very interested in speed things up :)
Is it possible, to bind repository definitions to different configurations and
create a configuration, where gradle uses its internal cache only?
I think about a counterpart of "mavenCentral()" - may be "gradleCache()" ?
Than I could create separate tasks like "buildWithOnlineCheck"
and "buildFromCache", or the like ...
compile- and jar-tasks of gradle take about factor 1,5 to 2 the time of ant -
so most of the time is spent with repository lookup.
Any hint is very appreciated!
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
