Hi Peter,
that was one of my presumptions, but I didn't tested it yet. Thank you.
I used the version matcher '+' because I don't want to check, if there
exists a new bugfix version.
Maven has a plugin which checks for new versions.
I voted for this issue: http://jira.codehaus.org/browse/GRADLE-774
And I hope you can optimize the following things someday.
1. If a task which need dependencies (compileJava, compileJavaTest,
test) has no input, then the resolving of the dependencies can be skipped.
2. If the dependencies are resolved for the compileJava tasks, then the
result can be used for the compileJavaTest task.
3. Enhance the profile report with the follwing two durations:
Ivy/Maven/Dependency
UP-TO-DATE check (reading, calculating, writing).
regards,
Mathias Kalb
Am 23.01.2011 01:58, schrieb Peter Niederwieser:
Mathias Kalb wrote:
But now (after more profiling) I think the dependencies are the main
problem.
The problem in this particular case is your excessive use of version
matchers, which causes lots of work for Ivy on each and every build. After
replacing version matchers with concrete versions (which you should do
anyway to gain control over your compile dependencies), the build time goes
down to seven seconds on my machine.
Cheers,
Peter
--
Peter Niederwieser
Developer, Gradle
http://www.gradle.org
Trainer& Consultant, Gradle Inc.
http://www.gradle.biz
Founder, Spock Framework
http://spockframework.org
--
PRODATO Integration Technology GmbH
Hauptstrasse 40, 91054 Erlangen
http://www.prodato.de
Mathias Kalb, Dipl.-Inf. (FH)
mailto:[email protected]
fon: +49-9131-612877
fax: +49-9131-612881
Sitz: Ebermannstadt, Registergericht Bamberg HRB 3748
Geschäftsführer: Dr. Michael Schlundt, Dr. Christian Meiler, Prof. Dr. Stefan
Jablonski
USt-IdNr. DE199384894
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
