[
https://issues.apache.org/jira/browse/MJAR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151382#comment-17151382
]
Luke Hutchison commented on MJAR-268:
-------------------------------------
I have no idea if Maven played a role or not in this bug, but I provided
reproduction instructions, and debugged the issue the best I could (without
success). I got rid of Moditect usage to work around the issue. This really
requires a Maven developer to step through the build process to figure out
where the CRC is getting corrupted. No zip library should ever produce a
zipfile with the wrong CRC.
> maven-jar-plugin records wrong CRC for manifest files
> -----------------------------------------------------
>
> Key: MJAR-268
> URL: https://issues.apache.org/jira/browse/MJAR-268
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Environment: Linux
> Reporter: Luke Hutchison
> Priority: Critical
> Fix For: waiting-for-feedback
>
>
> maven-jar-plugin records the wrong CRC for manifest files. This causes
> Sonatype to reject uploaded jarfiles.
> To reproduce:
>
> git clone [https://github.com/classgraph/classgraph.git]
> cd classgraph
> ./mvnw package
> unzip -t target/classgraph-4.8.56-SNAPSHOT.jar | head -2
>
> This gives the output:
>
> Archive: target/classgraph-4.8.56-SNAPSHOT.jar
> bad CRC a5cbb614 (should be 7ee23ce7)
> testing: META-INF/MANIFEST.MF bad CRC a5cbb614 (should be 7ee23ce7)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
