You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christoph Läubrich (Jira)" <ji...@apache.org> on 2023/09/20 10:41:00 UTC

[jira] [Commented] (MCOMPILER-544) ZipException: zip END header not found on POM dependency with Eclipse compiler

    [ https://issues.apache.org/jira/browse/MCOMPILER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767081#comment-17767081 ] 

Christoph Läubrich commented on MCOMPILER-544:
----------------------------------------------

I have the same problem and added now a possible fix here:
- https://github.com/apache/maven-compiler-plugin/pull/198

this resolves the issue for the compilation itself, but for test-compile-mojo there seems to be using a different approach, so I don't know if something similar is possible there ...

> ZipException: zip END header not found on POM dependency with Eclipse compiler
> ------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-544
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-544
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.11.0
>            Reporter: Václav Haisman
>            Priority: Major
>
> There is an impedance matching issue between Maven Compiler Plugin, [plexus-compiler-eclipse|https://github.com/codehaus-plexus/plexus-compiler/issues/302], and [eclipse.jdt.core|https://github.com/eclipse-jdt/eclipse.jdt.core/issues/1274]. m-c-p adds POM dependency's POM file to classpath, which makes it through plexus-compiler-eclipse to JDT and that prints an exception {{ZipException: zip END header not found}}. Arguably, m-c-p should not be adding non-JAR, non-wildcard-directory path to classpath for the compiler.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)