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] Updated: (DERBY-3989) Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment can't be found but a Java 6 environment can be
Date Tue, 08 Jun 2010 14:21:12 GMT

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

Kristian Waagan updated DERBY-3989:
-----------------------------------

    Attachment: derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff

That's a good point, Rick.

See attached patch 02-aa for a possible solution. It basically relaxes the conditions used
in the shouldNotSet-method. Earlier it kicked in only for IBM JDKs, no it will kick in regardless
of the JDK vendor as long as a Java 5 compiler is used with Java 6 libraries.
I also added some extra debugging prints.

Patch ready for review.

> Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment
can't be found but a Java 6 environment can be
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3989
>                 URL: https://issues.apache.org/jira/browse/DERBY-3989
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.1.1
>            Reporter: Rick Hillegas
>             Fix For: 10.5.1.1
>
>         Attachments: derby-3989-01-aa-optionalJava5.diff, derby-3989-01-ab-optionalJava5.diff,
derby-3989-01-ac-optionalJava5.diff, derby-3989-02-aa-dontUseJava6LibsWithJava5Compiler.diff
>
>
> This will make the build even more flexible. Probably involves the following changes:
> 1) Relaxing the requirement in PropertySetter that a Java 5 JDK must exist
> 2) Having PropertySetter look for a Java 6 JDK (and set java16compile.classpath accordingly)
just as PropertySetter looks for a Java 5 JDK today
> 3) Changing the setCompilerProperties target in the master build script so that it
>   a) requires that java15compile.classpath or java16compile.classpath is set (it's ok
for both to be set)
>   b) sets java15compile.classpath to ${jdbc3stubs}:${java16compile.classpath}

-- 
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