db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3117) Adjust master build script to require the Java 5 compiler to build Derby
Date Mon, 29 Oct 2007 15:42:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538525

Knut Anders Hatlen commented on DERBY-3117:

Rick, do we need to check vendor? If people want such fine-grained control, they could use
ant.properties instead. For people who only want to compile Derby, using the first JDK/SDK
we find would probably suffice. Note that setting compile.classpath does not change which
compiler we use, only which libraries the compiler uses to check that the methods/classes
we use exist. So the compiled byte code will look identical regardless of which vendor's class
library we use. The compiler only changes when we change JAVA_HOME.

> Adjust master build script to require the Java 5 compiler to build Derby
> ------------------------------------------------------------------------
>                 Key: DERBY-3117
>                 URL: https://issues.apache.org/jira/browse/DERBY-3117
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: BuildDefaults.txt, derby-3117-01-enforceJava5-aa.diff, derby-3117-01-enforceJava5-ab.diff,
derby-3117-01-enforceJava5-ac.diff, derby-3117-02-website-aa.diff, derby-3117-03-junit-aa.diff,
> Require the Java 5 compiler in order to build Derby as approved by the community recently:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message