taverna-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stian Soiland-Reyes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAVERNA-869) Require Java 8?
Date Mon, 01 Feb 2016 09:29:39 GMT

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

Stian Soiland-Reyes commented on TAVERNA-869:
---------------------------------------------

I updated all the Jenkins snapshot jobs at https://builds.apache.org/user/stain/my-views/view/taverna/
to use jdk-1.8.0 and triggered re-build - let's see if there are some syntactic issues coming
up. (typically bumping JDK minor version can cause an earlier compiler warning to become an
error)

> Require Java 8?
> ---------------
>
>                 Key: TAVERNA-869
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-869
>             Project: Apache Taverna
>          Issue Type: Bug
>          Components: Taverna Maven Parent
>    Affects Versions: parent 1
>            Reporter: Stian Soiland-Reyes
>            Assignee: Stian Soiland-Reyes
>              Labels: java
>             Fix For: parent 2
>
>
> Relating to TAVERNA-867 - would it now make sense to overall change Java requirement
to Java 8? 
> Our current compile setting says Java 7 for source compiling and target binary (JAR)
compatibility:
> https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml#L93
> I'm not suggesting this because of the doclint option - that could be fixed with a Maven
profile if we still wanted to support compiling on Java 7 - but because Java 7 has already
reached End of Life, and Java 8 has many nice new features that (with time) could be useful.
> Java 8 is now working fine on all 3 major OS-es, right? 



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

Mime
View raw message