harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5517) [classlib][archive] simplifying archive code by fixing manifest encoding to UTF-8
Date Thu, 13 Mar 2008 14:09:46 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578300#action_12578300
] 

Tim Ellison commented on HARMONY-5517:
--------------------------------------

My concern was that failing quietly means that you would get data that does not match the
original JAR file, and that could cause even greater confusion down stream -- so I was trying
to ensure that the failure happens early.

How about we agree that if we find a case of a JAR file with bogus data that would be safe
to ignore then we remove the IOException ?! <g>


> [classlib][archive] simplifying archive code by fixing manifest encoding to UTF-8
> ---------------------------------------------------------------------------------
>
>                 Key: HARMONY-5517
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5517
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Alexei Fedotov
>            Assignee: Tim Ellison
>             Fix For: 5.0M6
>
>         Attachments: remove_manifest_encoding.patch, remove_manifest_encoding_2.patch,
remove_manifest_encoding_3.patch
>
>
> By specification [1] manifests are encoded in UTF-8. There is no need to make code more
complex than that, so legacy of HARMONY-14 may be removed. Testing the patch.
> [1] http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message