Open GoogleCodeExporter opened 9 years ago
GoogleCodeExporter
commented
9 years ago It seems to be an issue with the new Java 7 implementation of ZipFile that uses
ZipCoder. Running IntelliJ with Ivyidea on Java 6 does not produce this error.
It seems that Java 7 zip implementation is not as tolerant as the previous oneOriginal comment by juri.ku...@gmail.com on 22 Oct 2013 at 11:11
GoogleCodeExporter
commented
9 years ago Did you zip some of the dependency jars yourself? It seems some encoding issue,
the 'jar' tool that ships with Java should do the job correctly, other tools
(like winzip, 7zip, ...) might not.Original comment by maarten....@gmail.com on 12 Nov 2013 at 11:59
GoogleCodeExporter
commented
9 years ago All jars are published using ivy itself. Running on Java 6. Actually there are
files with German umlauts that are packed with the jars.
Would you consider wrapping those malformed exceptions and provide the
dependency the plug-in is trying to resolve? Currently it is hard to find the
conflicting jar. We got dozens of them. I think there is not much more to do
for the ivyidea plug-in. MALFORMED as error message itself is not very helpful. Original comment by juri.ku...@gmail.com on 15 Nov 2013 at 8:06
GoogleCodeExporter
commented
9 years ago After taking a look at the code I don't think IvyIDEA can know which jar(s) are
causing this issue. It happens after resolving and somewhere deep inside
JetBrains code after the IvyIDEA plugin has made all the modifications to the
libraries.
IvyIDEA is able to resolve and download the dependencies, it goes wrong
somewhere inside JetBrains code where IntelliJ tries to read the jar (I guess
for indexing it). I think you'll have to open an issue at JetBrains to get a
more helpful error message. Sorry.Original comment by maarten....@gmail.com on 18 Nov 2013 at 11:04
GoogleCodeExporter
commented
9 years ago Thank you for your investigation, i try to collect more information and post it
at JetBrains. I'll report back a follow up link. Original comment by juri.ku...@gmail.com on 19 Nov 2013 at 7:56
Original issue reported on code.google.com by
juri.ku...@gmail.comon 15 Oct 2013 at 8:24