[
https://issues.apache.org/jira/browse/MJAR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885431#comment-17885431
]
Steven Schlansker commented on MJAR-313:
----------------------------------------
For reference, the Gradle devs state that because some tools assume the
manifest will be the first or second entry, it is also OK for them to do so and
will not change behavior, meaning the Maven-produced jars cannot be consumed
with Gradle:
https://github.com/gradle/gradle/issues/30589
> 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)
