Project

General

Profile

Actions

Architecture #5664

closed

Drop support for Java 6

Added by François ARMAND over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Category:
Architecture - Dependencies
Target version:
Effort required:

Description

Java 6 is an old, unsupported thing. It is EOL since February 2013, and had the bad side effect of NOT being open source.

This is only on the server.

We have to check that all supported distribution actually have a Java 7 available.

It will allow to 1/ actually stop using a non supported JVM, 2/ take as hypothesis JVM 1.7 and all the related optimisation available (FINALLY a real concept of Unix file and so no more fork for chmod, a more efficient bytecode, etc)


Subtasks 5 (0 open5 closed)

Architecture #5725: Change the compilation target in the pom.xml to Java 7ReleasedFrançois ARMAND2014-11-04Actions
Architecture #5730: Don't fork process anymore to change file permissionRejectedNicolas CHARLES2014-11-04Actions
Architecture #5760: Add a test on Java version in Rudder init script checking for Java 7 ReleasedBenoît PECCATTE2014-11-21Actions
Bug #5800: 3.0 Rpm server packages not building due to missing 'jetty-init-sles.patch'ReleasedBenoît PECCATTE2014-11-21Actions
Architecture #5782: The JDK/JRE dependency we use in the packages is not correctReleasedJonathan CLARKE2014-11-18Actions
Actions #1

Updated by François ARMAND over 6 years ago

  • Assignee set to Matthieu CERDA

I would LOVE to have, it could simplify a lot of things for us, Scala dev.

Actions #2

Updated by Nicolas CHARLES over 6 years ago

+1

Actions #3

Updated by Matthieu CERDA over 6 years ago

  • Status changed from New to 8

In the purpose of a smooth and friendly communication between you Scala devs and us UNIX sysadmins, I offer you in behalf of my team to study the OSes we support to see if your request is acceptable.

May the geat DevOps alliance live forever!

Actions #4

Updated by Matthieu CERDA over 6 years ago

  • Status changed from 8 to Discussion
  • Assignee changed from Matthieu CERDA to François ARMAND
OS version Java version Recent enough
Debian 7 1.7u65 (7u65-2.5.1-5~deb7u1)
RHEL 7 1.7u71 (1.7.0.71-2.5.3.1.el7_0)
RHEL 6 1.7u55 (1:1.7.0.55-2.4.7.1.el6_5)
Ubuntu 12.04 1.7u65 (7u65-2.5.1-4ubuntu1~0.12.04.2)
Ubuntu 14.04 1.7u65 (7u65-2.5.2-3~14.04)
SLES 11 Complicated (Depends on the SP) ?

The only OS that would eventually pose a problem is SLES 11, but SuSE stopped packaging Java due to license changes: https://www.novell.com/support/kb/doc.php?id=7010472

 As a result of a license change SUSE is no longer able to provide Oracle/Sun Java in the distribution or through the update channels.  As a result Java will need to be downloaded from the java.com site and manually installed.

This also means that we cannot provide support for Oracle Java.  Any support issues should be directed to Oracle.  The following information is provided as a potential solution but is not guaranteed.

SLES 12 will offer OpenJDK as a technology preview ( https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#fate-317917 ), so I guess it is reasonable to kindly ask SUSE user that they have to provide their own JDK (either from Oracle or from the SuSE build service)

So for me, dropping JRE 1.6 is OK, but I'd love JCL's or BPE's advice on this.

Actions #5

Updated by François ARMAND over 6 years ago

Thanks so much for the nice overwiew !

Actions #6

Updated by Benoît PECCATTE over 6 years ago

We already ask SLES user to install their own JRE, so this is perfectly reasonable.

Still, we'll have to be careful with the upgrade since users won't know that they have to manually upgrade java before upgrading rudder.
Maybe something like a pre-install script to warn them.

Actions #7

Updated by Matthieu CERDA over 6 years ago

  • Target version changed from 140 to 3.0.0~beta1
Actions #8

Updated by Jonathan CLARKE over 6 years ago

Benoît PECCATTE wrote:

We already ask SLES user to install their own JRE, so this is perfectly reasonable.

Still, we'll have to be careful with the upgrade since users won't know that they have to manually upgrade java before upgrading rudder.
Maybe something like a pre-install script to warn them.

+1!

Actions #9

Updated by Jonathan CLARKE over 6 years ago

  • Tracker changed from User story to Architecture
  • Status changed from Discussion to 12
Actions #10

Updated by Jonathan CLARKE over 6 years ago

  • Status changed from 12 to Pending release
Actions #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.

Actions

Also available in: Atom PDF