Bug #7348
closed
rudder-jetty initialisation should not support Java 6
Added by Jonathan CLARKE about 9 years ago.
Updated over 8 years ago.
Category:
System integration
Description
In #5664, we dropped support for Java 6. However, the script that launches jetty will still look for this version, and wrongly states that it is supported.
We should fix this, once the fix for #7345 is merged into the 3.0 branch (to avoid needless conflicts)
- Related to Bug #7345: JVM 8.0: warning about "Ignoring option PermSize=128m; support was removed in 8.0" added
- Assignee set to Jonathan CLARKE
- Target version changed from 2.10.20 to 3.0.12
- Target version changed from 3.0.12 to 3.0.13
- Target version changed from 3.0.13 to 3.0.14
- Target version changed from 3.0.14 to 3.0.15
- Target version changed from 3.0.15 to 3.0.16
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/938
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Related to Bug #8369: Rudder jetty init script broken on CentOS 7 added
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by