cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jburwell <>
Subject [GitHub] cloudstack pull request: [WIP][4.10+/long-term] Moving towards Jav...
Date Fri, 13 May 2016 13:46:24 GMT
Github user jburwell commented on the pull request:
    @rhtyd I think it would be a good idea to this PR up a bit.  I see three distinct pieces:
    1. **Spring 4 Upgrade**:  Spring 4 supports both Java7 and Java8.  Therefore, this upgrade
can be done without involving Java8.
    2. **Jetty Embedding**:  Again, Jetty 9 supports both Java7 and Java8.  Therefore, this
work can be done without involving Java8.
    3. **Java8**: Ideally, this piece should be fairly small -- disabling the F5 plugin, changing
the POMs, and a sundry of minor code changes to achieve compilation.
    The harder part is that all of these changes will require a full end-to-end test of the
    Finally, for Java8, I suggest that we follow the convention of many of Java-based projects
and remove the package dependencies on the JDK.  Some users choose to use OpenJDK and others
choose Oracle's JDK.  Therefore, the current dependency makes an invalid assumption about
the JDK users want to use -- making it more difficult to use the implementation of their choice.
    @wido as @rhtyd points out, Java8 is available via PPAs.  IMHO, Ubuntu's decision to keep
their distribution out-of-date is not a sufficient reason to continue requiring the use of
an unsupported Java runtime.  Given the number of significant security issues that have been
discovered in the JRE over the past few years, the longer we wait to upgrade to Java8, the
greater the risk that a significant security issue arises that forces CloudStack users to
either turn off their instances or run and hope no one hacks them.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message