You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Commented) (JIRA)" <ji...@apache.org> on 2012/01/02 18:08:30 UTC

[jira] [Commented] (JENA-177) If possible remove dependency to ICU4J by using Java built-in functionality

    [ https://issues.apache.org/jira/browse/JENA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178458#comment-13178458 ] 

Andy Seaborne commented on JENA-177:
------------------------------------

A clue, maybe.

When I tried upgrading from ICU4J 3.4.4 to any ICU4J that was newer during the release cycle, some tests started failing on punycode.  So, it maybe that the replacements are right and that we have dependency of old behaviour.

                
> If possible remove dependency to ICU4J by using Java built-in functionality
> ---------------------------------------------------------------------------
>
>                 Key: JENA-177
>                 URL: https://issues.apache.org/jira/browse/JENA-177
>             Project: Jena
>          Issue Type: Wish
>          Components: IRI, Jena
>            Reporter: Thorsten Möller
>            Priority: Minor
>         Attachments: IRI-icu4j.patch, IRI.patch, jena-icu4j.patch, jena2.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Jena-core and IRI currently depend on ICU4J for implementing Unicode support. Since ICU4J is rather heavyweight of which a rather small fraction is used, we should check if there is a way of implementing the functionality in an alternative way, either by (i) using built-in (standard) Java classes, (ii) other libraries that are already dependencies, or (iii) in a completely alternative way. This is also supported by the fact that since relevant parts have been initially implemented, Unicode support has been considerably extended in Java, see http://java.sun.com/developer/technicalArticles/javase/i18n_enhance/.

--
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