[
https://issues.apache.org/jira/browse/SLING-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150597#comment-13150597
]
Bertrand Delacretaz commented on SLING-2288:
--------------------------------------------
The jar file spec doesn't seem to mention this, but the jar tool docs [1]
indicates that jar always puts the manifest first in the jar.
https://issuetracker.springsource.com/browse/BNDLR-287 mentions that
JarInputStream does enforce it while JarFile does not - I haven't checked that
myself in the current JDKs.
So it looks like it's really a de facto requirement, and logging a warning is
the right thing to do to avoid surprises.
[1] http://download.oracle.com/javase/1.3/docs/tooldocs/solaris/jar.html
> Bundle jar is silently ignored by the installer if MANIFEST.MF is not the
> first file in the archive
> ---------------------------------------------------------------------------------------------------
>
> Key: SLING-2288
> URL: https://issues.apache.org/jira/browse/SLING-2288
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Priority: Minor
>
> A jar file where the MANIFEST.MF is not the first file in the jar is silently
> ignored by the installer.
> We should at least output a warning, and maybe try harder to find the
> manifest, in the Util.getManifest(...) method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
