[
https://issues.apache.org/jira/browse/MJAR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885449#comment-17885449
]
Steven Schlansker commented on MJAR-313:
----------------------------------------
I am able to see the problem withÂ
{code:java}
jdbi% mvn -am -pl core clean package -DskipTests && jar tf
core/target/jdbi3-core-*.jar{code}
That said, we do post-process our jars with the somewhat bespoke
`inline-maven-plugin`:
[https://github.com/basepom/inline-maven-plugin]
By commenting that out, the jar ordering is restored.
So maybe this is an issue with inline-maven-plugin, not jar-maven-plugin. I'll
follow up with the plugin maintainer and see what he thinks.
> 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)
