[GRADLE-3131] Weird Java compile errors when build is run with --parallel on Apple JDK 6 Created: 09/Jul/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 2.0
Fix Version/s: None

Type: Bug
Reporter: Peter Niederwieser Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Problem goes away when switching to OpenJDK 7, or when using `compileJava.options.fork = true; compileJava.options.forkOptions.executable = 'path/to/apple/jdk6/javac'`. Hence I'm guessing that the problem is related to multi-threaded use of JDK compiler API on Apple JDK 6 (or perhaps also Oracle JDK 6). I don't have a reproducible example, but here is some more information:

% java -version                                                                                                                                                                                                                                                                       
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
% ./gradlew -v                                                                                                                                                                                                                                                                        
Gradle 1.12

Build time:   2014-04-29 09:24:31 UTC
Build number: none
Revision:     a831fa866d46cbee94e61a09af15f9dd95987421

Groovy:       1.8.6
Ant:          Apache Ant(TM) version 1.9.3 compiled on December 23 2013
Ivy:          2.2.0
JVM:          1.6.0_65 (Apple Inc. 20.65-b04-462)
OS:           Mac OS X 10.9.1 x86_64
% ./gradlew classes --parallel
/Volumes/Data/Users/xxx/trunk/xxx/util/Util.java:1415: cannot access java.util.concurrent.ScheduledFuture
class file for java.util.concurrent.ScheduledFuture not found
            return mme.foundation.util.ScheduledThreadPoolExecutorUtil.scheduleToRunOnce(runnable, runAfter, timeUnit);

Some of the other compile errors we get look fairly normal (e.g. as if compile class path was missing a dependency), others are weird like the one above (e.g. we once saw something like "'{' not expected here").

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:40:48 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.