Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-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 7A5C4D071 for ; Tue, 6 Nov 2012 16:18:16 +0000 (UTC) Received: (qmail 28149 invoked by uid 500); 6 Nov 2012 16:18:16 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 27926 invoked by uid 500); 6 Nov 2012 16:18:15 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 27766 invoked by uid 99); 6 Nov 2012 16:18:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 16:18:13 +0000 Date: Tue, 6 Nov 2012 16:18:13 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: <553453976.74961.1352218693257.JavaMail.jiratomcat@arcas> In-Reply-To: <654657780.74958.1352218692629.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DERBY-5984) Derby 10.8 branch does not build out-of-the-box using Oracle's Java 7 JDK on Mac OSX. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491579#comment-13491579 ] Rick Hillegas commented on DERBY-5984: -------------------------------------- Note that I can successfully build the 10.9 branch using Java 7 on Mac OSX. > Derby 10.8 branch does not build out-of-the-box using Oracle's Java 7 JDK on Mac OSX. > ------------------------------------------------------------------------------------- > > Key: DERBY-5984 > URL: https://issues.apache.org/jira/browse/DERBY-5984 > Project: Derby > Issue Type: Bug > Components: Build tools > Affects Versions: 10.8.1.2, 10.8.2.2, 10.8.3.0 > Reporter: Rick Hillegas > > If I try to build the 10.8 branch using Oracle's Java 7 for Mac OSX, the build fails as follows: > [setJdkProperties] Unrecognized VM vendor: 'Oracle Corporation' > [setJdkProperties] An attempt to configure the required JDKs will be made, but the build may fail. > [setJdkProperties] In case of problems: > [setJdkProperties] - consult BUILDING.html and set the required properties manually > [setJdkProperties] - set the property printCompilerProperties to true and ask the Derby development community for help > [setJdkProperties] (please provide the debug output from running ant) > BUILD FAILED > /Users/rh161140/derby/branches/10.8/build.xml:241: Don't know how to set java15compile.classpath, java16compile.classpath using this environment: > java.vendor = Oracle Corporation > java.home = /Library/Java/JavaVirtualMachines/jdk1.7.0_09.jdk/Contents/Home/jre > java.version = 1.7.0_09 > os.name = Mac OS X > j14lib = null > j15lib = null > j16lib = null > jdkSearchPath = /Library/Java/JavaVirtualMachines/jdk1.7.0_09.jdk/Contents > Please consult BUILDING.html for instructions on how to set the compiler-classpath properties. > Total time: 1 second > The following facts about this branch do not seem to me to be consistent: > 1) The release notes for 10.8.1, 10.8.2, and 10.8.3 state that JDBC 4.1 is a supported JDBC level, which implies support for Java 7. > 2) The release notes for all 3 releases also state that Java SE versions are supported from 1.4 on up. Since 10.8.2 and 10.8.3 were released after Java 7 went live, this implies that those releases support Java 7. > 3) But you can't build the source distribution of 10.8.3 using Java 7 on a major platform. > I don't think that 10.8.3 is worse than 10.8.2 in this regard so I would not flunk the 10.8.3 candidate for this defect. However, we should try to fix this problem in case we need to build another 10.8 release candidate. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira