james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Resolved] (MIME4J-159) Update CharsetUtil to java5. Some of CharsetUtil is no more "useful" as it was a java 1.3 backport of java2 1.4-5 stuff.
Date Thu, 14 Apr 2011 15:11:06 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski resolved MIME4J-159.
--------------------------------------

    Resolution: Fixed

Removed custom charset registry dated back to Java 1.3 in favour of Java 1.4+ standard Charset
implementation.

Oleg  

> Update CharsetUtil to java5. Some of CharsetUtil is no more "useful" as it was a java
1.3 backport of java2 1.4-5 stuff.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MIME4J-159
>                 URL: https://issues.apache.org/jira/browse/MIME4J-159
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>    Affects Versions: 0.6
>            Reporter: Stefano Bagnara
>            Assignee: Oleg Kalnichevski
>            Priority: Minor
>             Fix For: 0.7
>
>
> Some method is not used at all.
> The way it statically fills the decodingSupported/encodingSupported sets is more easily
implemented using java5 Charset methods.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message