incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Steer (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (JENA-177) If possible remove dependency to ICU4J by using Java built-in functionality
Date Wed, 04 Jan 2012 22:27:40 GMT


Damian Steer resolved JENA-177.

       Resolution: Fixed
    Fix Version/s: Jena 2.7.1
         Assignee: Damian Steer

Fixed in jena 2.7.1, IRI 0.9.1 and jena-top 1.

There's a slight bootstrapping issue in that we need to get jena-top out before icu4j will
actually disappear.
> 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
>            Assignee: Damian Steer
>            Priority: Minor
>             Fix For: Jena 2.7.1
>         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

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