[jira] [Assigned] (GUACAMOLE-635) Build against and require Java 1.8

["Michael Jumper (JIRA)" <ji...@apache.org>]

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

Michael Jumper reassigned GUACAMOLE-635:
----------------------------------------

    Assignee: Michael Jumper

> Build against and require Java 1.8
> ----------------------------------
>
>                 Key: GUACAMOLE-635
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-635
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Major
>             Fix For: 1.0.0
>
>
> As discussed on [PR #319 for GUACAMOLE-220|https://github.com/apache/guacamole-client/pull/319#discussion_r219670482], and as [discussed on the dev@ mailing list|https://lists.apache.org/thread.html/874edd3a19b0cf0302cbb56f2406f6050cf4296dc31703aa34b30be6@%3Cdev.guacamole.apache.org%3E], continuing to support Java 1.6 at all levels of guacamole-client makes less and less sense:
> * Java 1.6 reached end-of-life some time ago.
> * Java 1.7 has ceased receiving further public updates.
> * Other mainstream projects which rely on Java have already moved on to 1.7+.
> Though guacamole-common should likely remain as compatible as possible, moving all other Java components forward to a 1.8 build seems best, with the upcoming major 1.0.0 release being an ideal time.
> The only non-EOL Linux distribution I've been able to find so far that lacks Java 1.8 is Ubuntu 14.04 LTS, which is reaching EOL in April 2019.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)