db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4699) Build breaks if a Java 6 JDK is detected when compiling with a Java 5 compiler
Date Mon, 21 Jun 2010 13:28:22 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan resolved DERBY-4699.
------------------------------------

    Fix Version/s: 10.6.1.1
                   10.7.0.0
       Resolution: Fixed

Committed to trunk with revision 954421.
Back-ported to the 10.6 branch with revision 956576.

> Build breaks if a Java 6 JDK is detected when compiling with a Java 5 compiler
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-4699
>                 URL: https://issues.apache.org/jira/browse/DERBY-4699
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.7.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.6.1.1, 10.7.0.0
>
>
> If a Java 6 JDK is detected by PropertySetter when compiling with a Java 5 compiler,
the build break because classes with an unsupported class format version are pulled in.
> PropertySetter already has code to fail the build or ignore the Java 6 libraries for
IBM JDKs.
> This issue is a straw man issue for the patch posted under DERBY-3989 (' derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff').

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


Mime
View raw message