Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 51AE819FB4 for ; Fri, 1 Apr 2016 18:02:32 +0000 (UTC) Received: (qmail 39383 invoked by uid 500); 1 Apr 2016 18:02:31 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 39324 invoked by uid 500); 1 Apr 2016 18:02:31 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 39313 invoked by uid 99); 1 Apr 2016 18:02:31 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Apr 2016 18:02:31 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 65108DFDE0; Fri, 1 Apr 2016 18:02:31 +0000 (UTC) From: jburwell To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack pull request: maven: Upgrade dependency versions Content-Type: text/plain Message-Id: <20160401180231.65108DFDE0@git1-us-west.apache.org> Date: Fri, 1 Apr 2016 18:02:31 +0000 (UTC) Github user jburwell commented on the pull request: https://github.com/apache/cloudstack/pull/1397#issuecomment-204494886 @swill Java8 is not currently supported by the management server. We know that the process will collapse after running for 24-48 hours. Part of the issue is that Spring 3 has known issues on Java8. Per my earlier feedback, I think the Bouncy Castle upgrade should be split into a separate PR. The issue could be with the changes to the certificate handling code or an issue between the new Bouncy Castle version and one of the transitive dependency updates. Breaking up this PR would make it much easier to understand whether or not this issue is caused by the dependency upgrades or the code change. --- 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 infrastructure@apache.org or file a JIRA ticket with INFRA. ---