Hello,
I got a bit further with my investigations and it looks like most errors, I
reported, where related to gradles internal caching.
The error about failing junit-tests was related to older jarfiles from my
projects, that have been cached and probabely misused.
With today tests, I removed all .gradle directories from the projects, removed
all project-jars from local repository and removed anything related to my
projects from ~/.gradle/cache (rm -rf ~/gradle/cache/{*de.schwarzrot*,
*unspecified*} ).
Then the build works, but whenever I forgot to remove all cached stuff,
strange things happened. I have no idea, which of the removal is really
necessary, so I do all. So - I beg your pardon - but I'm not convinced yet,
that incremental gradle builds are reliable. But I admit, that it's hard to
get rid of without making errors.
After all I think, gradle is a good base, I can live with, so there's no need
to think about the way back ;)
Just have to learn to deal with the pitfalls.
How about your git repository? When will it reflect the preview sources?
or is there another way to stay up-to-date with your ultimative changes?
I tried to update the dependency of groovy for buildSrc/build.gradle from
1.7.0 to 1.7.1 - but then I get:
- unresolved dependency: org.fusesource.jansi#jansi;1.1: not found
That must be a transient dependency of groovy or the like, I did not code that
dependency.
I got sometimes strange exceptions from my version class, which made me
suspect, that gradle checks project dependencies from rootproject
build.gradle on building its own classes from buildSrc. I'm sorry, but
currently I can't reproduce it - so I don't have further informations.
Just to understand the buildscripts - what happens, when I have 2 sections of
i.e. "allprojects" and additionally a section "subprojects" - when will the
build.gradle of a subproject get evaluated?
The point is, I have a working-dir definition for the test task in a file,
that will be imported in all build.gradle files. Now I'd like to overwrite
that working directory for just one subproject.
I tried to use "test.doLast", but I guess, that definition will be evaluated
before the "normal" setting of the working directory, wich looks like:
test {
workingDir = ...
}
Is there a way to code the setting of the working directory (with multiple
overriding) independant of the time of evaluation?
kind regards
Geronimo
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
