incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Möller (Commented) (JIRA) <>
Subject [jira] [Commented] (JENA-177) If possible remove dependency to ICU4J by using Java built-in functionality
Date Mon, 19 Dec 2011 12:59:30 GMT


Thorsten Möller commented on JENA-177:

BTW, ICU4J is modularized, meaning that it provides options to build smaller ICU4J modules,
see Seems that the "Normalizer" module would
be sufficient, provided that DNS name normalization is moved to available since
JDK1.6 (as done by the patch).

This would be another option to reduce the overhead in case entirely factoring out ICU4J is
not possible at the moment. Unfortunately, I'm not aware of a Maven repository that already
contains ICU4J modules. Is there an ASF Maven repository, and would it be an option to upload
an ICU4J module?
> If possible remove dependency to ICU4J by using Java built-in functionality
> ---------------------------------------------------------------------------
>                 Key: JENA-177
>                 URL:
>             Project: Jena
>          Issue Type: Wish
>          Components: IRI, Jena
>            Reporter: Thorsten Möller
>            Priority: Minor
>         Attachments: IRI.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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message