You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "Werner Keil (JIRA)" <ji...@apache.org> on 2015/12/08 17:15:11 UTC
[jira] [Commented] (TAMAYA-113) Remove Java 8 related parts
[ https://issues.apache.org/jira/browse/TAMAYA-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15047025#comment-15047025 ]
Werner Keil commented on TAMAYA-113:
------------------------------------
Sounds like a good idea, based on the experience with JSR 363 (where a single API works all the way from Java ME 8 Embedded to Java EE 6, 7 or 8)
Are there containers btw that would also require Java EE/SE 6 on the API, or is JDK 7 fine as the lower margin?
In most cases it might just be Diamond expressions that are a major difference ;-)
> Remove Java 8 related parts
> ---------------------------
>
> Key: TAMAYA-113
> URL: https://issues.apache.org/jira/browse/TAMAYA-113
> Project: Tamaya
> Issue Type: Improvement
> Components: API, Docs
> Reporter: Anatole Tresch
> Assignee: Anatole Tresch
> Fix For: 0.2-incubating
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The Java 8 specific API does not add much benefit. The Java 7 based API can similarly be used in Java 8 and Optional can still be used with Java8 initialized with the value returned from the Tamaya API. So the java7/java8 separation should be removed and the overall project tree be based on the Java 7 version. The Java 8 related parts are moved to an attic directory, and later they may even be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)