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

Kristian Waagan commented on DERBY-4263:
----------------------------------------

Hi Myrna,

Maybe you could run with -DprintCompilerProperties=true and post the output 
from the target setting the classpaths?
If you do that with trunk first, and then again after commenting out the lines 
mentioned below, we could compare and see what has changed. If it's the same, I 
must have changed something else in the build process.

To go back to old behavior, assuming the required JDKs are available, comment 
out the calls to the method 'setForMostJDKsJARInspection' (only two of the 
three should do, but commenting out all three doesn't hurt).
If you pipe to less, the interesting information should be found on the first 
page and onwards.

> PropertySetter isn't able to recognize JDK without version number in path
> -------------------------------------------------------------------------
>
>                 Key: DERBY-4263
>                 URL: https://issues.apache.org/jira/browse/DERBY-4263
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.6.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         Attachments: derby-4263-1a-jdk_detection_by_jars.diff, 
> derby-4263-1b-jdk_detection_by_jars.diff
>
>
> With empty ant.properties and JDK 6 installed in /tmp/jdk as the only JDK on 
> the system, PropertySetter complains that it's not able to set 
> java16compile.classpath:
> ,----
> | [setJdkProperties] 
> | [setJdkProperties] PropertySetter environment =
> | [setJdkProperties] 
> | [setJdkProperties] java.vendor = Sun Microsystems Inc.
> | [setJdkProperties] java.home = /tmp/jdk/jre
> | [setJdkProperties] java.version = 1.6.0_13
> | [setJdkProperties] os.name = SunOS
> | [setJdkProperties] j14lib = null
> | [setJdkProperties] j15lib = null
> | [setJdkProperties] j16lib = null
> | [setJdkProperties] 
> | 
> | BUILD FAILED
> | /code/derby/trunk0/build.xml:203: Don't know how to set 
> java15compile.classpath, java16compile.classpath using this environment:
> | 
> | java.vendor = Sun Microsystems Inc.
> | java.home = /tmp/jdk/jre
> | java.version = 1.6.0_13
> | os.name = SunOS
> | j14lib = null
> | j15lib = null
> | j16lib = null
> `----
> Since it is able to detect both that the version of the default JDK is 
> 1.6.0_13 and where it is installed, setting java16compile.classpath should be 
> trivial.
> If the name of the JDK directory is changed from /tmp/jdk to /tmp/jdk1.6.0, 
> Derby is built successfully.

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

Reply via email to