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-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, 13 Jan 2009 08:55:02 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663270#action_12663270
] 

Knut Anders Hatlen commented on DERBY-3989:
-------------------------------------------

Silly question, but... Does it work without the patch? If I understand the comments on DERBY-3988
correctly, the combination of the IBM 1.5 compiler and java16compile.classpath pointing to
IBM 1.6 doesn't work. According to those comments, the build should have printed a message
telling you to use a Java 6 compiler. I'm wondering if the build doesn't emit that message
because java16compile.classpath was set implicitly from j16lib, and the build scripts should
be updated to check both java16compile.classpath and j16lib in checkForProblematicSettings().

> 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.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-3989-01-aa-optionalJava5.diff, derby-3989-01-ab-optionalJava5.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