[
https://issues.apache.org/jira/browse/CLOUDSTACK-9710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822380#comment-15822380
]
ASF GitHub Bot commented on CLOUDSTACK-9710:
--------------------------------------------
Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1888
BTW, something that is worth noting is that even if you use a new system vm
template, but the box that the vm template was built on is running Java 7, you
will get the same error that @syed just reported. I forgot to update my
Jenkins slave to use Java 8 and I was able to reproduce the problem that @syed
experienced with new builds of the system vm template. Maybe we should try to
put a check or something if you try to build the system vm template with the
wrong version. I am sure people will run into this because almost everyone
will be using Java 7 in their Jenkins for previous ACS builds and I am sure
others will forget to make the change to use Java 8 for those builds.
Building the ACS RPMs will fail if you don't have Java 8 installed, but the
system VM build will succeed even though the resulting template will not be
functional...
> Switch to JDK 1.8
> -----------------
>
> Key: CLOUDSTACK-9710
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9710
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: Future, 4.10.0.0
>
>
> Switch to using JDK1.8 by default for building and running CloudStack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
