You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2010/04/09 20:09:51 UTC
[jira] Created: (BUILDR-422) Make sure MANIFEST.MF is the first
entry of the jar
Make sure MANIFEST.MF is the first entry of the jar
---------------------------------------------------
Key: BUILDR-422
URL: https://issues.apache.org/jira/browse/BUILDR-422
Project: Buildr
Issue Type: Improvement
Components: Packaging
Affects Versions: 1.4
Reporter: Antoine Toulme
Fix For: 1.4.1
MANIFEST.MF should always be the first entry of the jar. At a minimum we want a spec that makes sure of that. This is critical for performance or even for Java to read manifests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-422) Make sure MANIFEST.MF is the first
entry of the jar
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-422.
-----------------------------------
Fix Version/s: 1.4
(was: 1.4.1)
Resolution: Fixed
OK, added spec, it passes alright.
09:19:25~/w/buildr>svn ci spec/java/packaging_spec.rb -m "fix for BUILDR-422 Make sure MANIFEST.MF is the first entry of the jar"
Sending spec/java/packaging_spec.rb
Transmitting file data .
Committed revision 932753.
> Make sure MANIFEST.MF is the first entry of the jar
> ---------------------------------------------------
>
> Key: BUILDR-422
> URL: https://issues.apache.org/jira/browse/BUILDR-422
> Project: Buildr
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 1.4
> Reporter: Antoine Toulme
> Assignee: Antoine Toulme
> Fix For: 1.4
>
>
> MANIFEST.MF should always be the first entry of the jar. At a minimum we want a spec that makes sure of that. This is critical for performance or even for Java to read manifests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (BUILDR-422) Make sure MANIFEST.MF is the first
entry of the jar
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme reassigned BUILDR-422:
-------------------------------------
Assignee: Antoine Toulme
> Make sure MANIFEST.MF is the first entry of the jar
> ---------------------------------------------------
>
> Key: BUILDR-422
> URL: https://issues.apache.org/jira/browse/BUILDR-422
> Project: Buildr
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 1.4
> Reporter: Antoine Toulme
> Assignee: Antoine Toulme
> Fix For: 1.4.1
>
>
> MANIFEST.MF should always be the first entry of the jar. At a minimum we want a spec that makes sure of that. This is critical for performance or even for Java to read manifests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-422) Make sure MANIFEST.MF is the first
entry of the jar
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855510#action_12855510 ]
Antoine Toulme commented on BUILDR-422:
---------------------------------------
It looks like the current behavior of Buildr is actually correct, but there is no spec I could quickly find that checks it. I will add a spec for it.
> Make sure MANIFEST.MF is the first entry of the jar
> ---------------------------------------------------
>
> Key: BUILDR-422
> URL: https://issues.apache.org/jira/browse/BUILDR-422
> Project: Buildr
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 1.4
> Reporter: Antoine Toulme
> Assignee: Antoine Toulme
> Fix For: 1.4.1
>
>
> MANIFEST.MF should always be the first entry of the jar. At a minimum we want a spec that makes sure of that. This is critical for performance or even for Java to read manifests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.