[GRADLE-3426] Incremental Java compilation does not work when dependencies use Java 1.2 bytecode Created: 01/Apr/16  Updated: 02/Feb/17  Resolved: 02/Feb/17

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

Type: Bug
Reporter: Sterling Greene Assignee: Unassigned
Resolution: Duplicate Votes: 0


 Description   

https://discuss.gradle.org/t/could-not-expand-zip-error-while-using-incremental-java-compilation/15689

com.ibm.icu:icu4j:2.6.1 has classes compiled with Java 1.1 and Java 1.2. When this jar is on the classpath, the incremental snapshotter fails with a ArrayIndexOutOfBoundsException deep down in ASM code. I tried splitting this jar into 1.1 classes and 1.2 classes. 1.1-only jar works. 1.2-only jar does not.

 Comments   
Comment by Scott Palmer [ 11/Jul/16 ]

I saw a similar error while trying to use the jmh plugin (id "me.champeau.gradle.jmh" version "0.3.1") :

Execution failed for task ':jmhJar'.
> Could not expand ZIP 'C:\Users\scott.palmer\.gradle\caches\modules-2\files-2.1\org.hamcrest\hamcrest-core\1.1\860340562250678d1a344907ac75754e259cdb14\hamcrest-core-1.1.jar'.

In my case the exception was different though:
Caused by: org.gradle.api.file.DuplicateFileCopyingException: Encountered duplicate path "org/hamcrest/BaseDescription.class" during copy operation configured with DuplicatesStrategy.FAIL
at org.gradle.api.internal.file.copy.DuplicateHandlingCopyActionDecorator$1$1.processFile(DuplicateHandlingCopyActionDecorator.java:53)
at org.gradle.api.internal.file.copy.CopyFileVisitorImpl.processFile(CopyFileVisitorImpl.java:60)
at org.gradle.api.internal.file.copy.CopyFileVisitorImpl.visitFile(CopyFileVisitorImpl.java:44)
at org.gradle.api.internal.file.AbstractFileTree$FilteredFileTreeImpl$1.visitFile(AbstractFileTree.java:150)
at org.gradle.api.internal.file.archive.ZipFileTree.visit(ZipFileTree.java:91)
... 85 more

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 Sterling Greene [ 02/Feb/17 ]

Migrated to https://github.com/gradle/gradle/issues/1305

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