This hasn't been reported before.
There are a few different ways that Gradle can manage the Java compiler.
Are there any custom settings on the JavaCompile task? like using a
different javac executable? setting useAnt = true?
Xavier Ducrohet <mailto:x...@google.com>
12 February 2014 11:01 am
Hello,
I have a project with 70ish projects and I'm trying to run with
--parallel and I keep getting errors (this is with 1.10). A lot of
those projects are android projects, there's also a lot of custom
logic in some of the projects (either regular java projects or on top
of the android plugin).
Every time I get an error it's also during a compileJava task, either
in an Android project or in a Java project.
The weird part is that the error never makes sense. For example we
have the source of the jsr305 lib in our tree (we're using it from
source) and I'll get errors like:
/path/to/src/main/java/javax/annotation/CheckForSigned.java:1: class,
interface, or enum expected
package javax.annotation;
^
Obviously this file is correct, and compiles fine without
parallelization. All breakages I've seen are always the same and
always in the Java compile task on code that is not broken.
Is this is a known issue? Are there specifics to projects configs and
inter-projects dependencies that could trigger this?
I have another projects that is about 20ish java-only projects and I
don't have any issue building it in parallel but it has basically no
custom logic to build it.
thanks
Xavier
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
