[
https://issues.apache.org/jira/browse/MCOMPILER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767404#comment-17767404
]
ASF GitHub Bot commented on MCOMPILER-544:
------------------------------------------
laeubi commented on PR #198:
URL:
https://github.com/apache/maven-compiler-plugin/pull/198#issuecomment-1728937585
> Cen we add example from jira as IT?
I'm not that familiar with compiler-itests but it should be enough to check
that no ERROR printout is there when executing the given pom example on a
project that has at least one dummy source file so compilation is triggered...
> 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)
