Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write manifest file first in update-jar! #716

Merged
merged 1 commit into from
Nov 4, 2019

Conversation

RadicalZephyr
Copy link
Contributor

It appears to be a de facto standard for the meta-inf directory and the manifest.mf file to be the first and second entries in the jar file.

There is no mention of ordering in the jar specification, but it appears that most tools create Jar files with the manifest file as the first entry by using this JarOutputStream constructor. In addition the complementary jar reading code in JarInputStream explicitly states that it assumes the first few entries contain the manifest file.

At least one other tool is known to rely on this detail of jar file ordering.

While it may not be necessary according to the spec, it seems reasonable to follow this fairly standard ecosystem behavior.

This fixes #710.

It appears to be a de facto standard for the meta-inf directory and
the manifest.mf file to be the first and second entries in the jar
file.
@burn2delete burn2delete merged commit 64334b4 into boot-clj:master Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

jar file generated by "jar" task is not compatible with Capsule
2 participants