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 (JIRA)" <ji...@apache.org> on 2015/05/06 23:23:00 UTC

[jira] [Resolved] (JENA-931) Shift org.apache.jena.atlas in jena-base onto Java 8 types

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

Andy Seaborne resolved JENA-931.
--------------------------------
       Resolution: Fixed
    Fix Version/s: Jena 3.0.0
         Assignee: Andy Seaborne

> Shift org.apache.jena.atlas in jena-base onto Java 8 types
> ----------------------------------------------------------
>
>                 Key: JENA-931
>                 URL: https://issues.apache.org/jira/browse/JENA-931
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Jena
>    Affects Versions: Jena 3.0.0
>            Reporter: A. Soroka
>            Assignee: Andy Seaborne
>              Labels: Java8, typesystem
>             Fix For: Jena 3.0.0
>
>
> Several types in org.apache.jena.atlas in module jena-base duplicate the semantics of types introduced in Java 8, e.g. Jena's Transform is substantially the same as Java 8's Function, Jena's Filter is substantially the same as Java 8's Predicate, etc.
> When this ticket is done, all such types will subtype the appropriate Java 8 types, will be deprecated, and will no longer be used inside the Jena code base. A further ticket may lead to actual removal of those deprecated types, at a convenient  future moment and in a non-disruptive fashion.
> Where possible, declarations and uses of similar types throughout the Jena code base should be converted to use the types in o.a.j.atlas, for clarity and concision. Some such migration of this kind can occur as part of this ticket, although a wholesale shift onto o.a.j.atlas may take some time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)