Hi Jerod,
On Aug 11, 2008, at 7:53 PM, JerodLass wrote:
I just ran into a slight issue with gradle. I would like to do some
dependency management, including altering the manifest class-path,
updating
eclipse files (since my project is in transition), and some other
small
items. I would like to do this after compiling because I use the
list of
resolved dependencies, but before libs because some files need to be
included with the libs.
I made a manageDependencies task that I hooked in to depend on
compile, then
set libs to depend on manageDependencies. With this configuration,
a build
took around 420 seconds for a project with 25-30 subprojects. When I
changed so that the new build logic executes at the end of the
compile task,
the project built in around 160 seconds. Is this normal?
It shouldn't be. Does the time increase before the first task gets
executed?
If so, adding
tasks to multi-project java projects becomes somewhat unrealistic.
There
are enough tasks already to hook into, but to make the output more
readable
it would be nice for new tasks to be easier.
Definitely. Adding tasks is a basic operation that should not be
expensive.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
