db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4263) PropertySetter isn't able to recognize JDK without version number in path
Date Thu, 13 Aug 2009 20:49:14 GMT

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

Myrna van Lunteren commented on DERBY-4263:
-------------------------------------------

Well, I needed to do the cleanup to figure out what was actually happening.

So, there is one strange thing; it *is* reporting this for my IBM 1.6 jvm (SR5 sdk, I've got
a couple of the same installs in different directories)
[setJdkProperties] found JDK: vendor=unknown, specVersion=unknown, implVersion=6.0, path=c:\jvms\ibm16

While for the 1.5 ibm jvms it reports:
[setJdkProperties] found JDK: vendor=IBM Corporation, specVersion=1.5.0, implVersion=1.5.0,
path=c:\jvms\ibm15

Note, that if I just try to run my trusty, rusty program that spits out all properties set
by the jvm, it reports 
key: java.vm.vendor	;value: IBM Corporation
key: java.vendor	;value: IBM Corporation
key: java.specification.version	;value: 1.6
key: java.vm.specification.version	;value: 1.0
key: java.specification.name	;value: Java Platform API Specification

My build was setup up without setting java16compile.classpath (to the ibm16 jars) before the
change. If I physically  remove the sun jdk 1.6 I have, It does pick up the ibm jvm and my
build works as before...(i.e. pick up the IBM 1.6 that's there).
If I set java16compileclasspath it also picks up the ibm16.
The sun 1.6 is [setJdkProperties] found JDK: vendor=Sun Microsystems, Inc., specVersion=1.6,
implVersion=1.6.0_01, path=c:\jvmsjdk16
(java -version gives: java version "1.6.0_01"
                                    Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
                                    Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed
mode) )

A little debugging  and it seems the propertySetter thinks my (1.6) vendor is null.
I'll try to find some time to debug this further, figure out why.

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


Mime
View raw message