[
https://issues.apache.org/jira/browse/MJAR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885439#comment-17885439
]
Attila Kelemen commented on MJAR-313:
-------------------------------------
[~sjaranowski] I have no other example. I personally just care about this only
because this way I can't use JDBI with JPMS, but have no idea what is the exact
cause. If I had to make a guess, because of the addition of the manifest
entries to the jar plugin in [the parent
pom.xml|https://github.com/jdbi/jdbi/blob/eb158ad5db59983b790340b6002ba439fe99ad57/internal/build/pom.xml#L1063]
in a separate config, Maven removes the manifest and reads it to the end of
the zip. That said, this is just a wild speculation on my part with nothing to
back it up.
> maven-jar-plugin sometimes doesn't add MANIFEST.MF as 1st or 2nd entry
> ----------------------------------------------------------------------
>
> Key: MJAR-313
> URL: https://issues.apache.org/jira/browse/MJAR-313
> Project: Maven JAR Plugin
> Issue Type: Bug
> Reporter: Attila Kelemen
> Priority: Major
>
> In certain situations (not sure what is the exact condition required), the
> Maven jar plugin doesn't add the _MANIFEST.MF_ as the 1st or 2nd entry. This
> can be a problem (even though technically the spec doesn't have such a
> requirement), because such a jar file cannot be read with the core JDK class
> {{JarInputStream}}.
> A project this can be reproduced with is JDBI. See the
> [https://github.com/jdbi/jdbi/issues/2698] for details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
