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] Issue Comment Edited: (DERBY-4263) PropertySetter isn't able to recognize JDK without version number in path
Date Wed, 12 Aug 2009 19:39:14 GMT

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

Myrna van Lunteren edited comment on DERBY-4263 at 8/12/09 12:37 PM:
---------------------------------------------------------------------

The difference was that after your change, it picked a Sun 1.6 instead of an IBM 1.6 jvm.

The environment where I saw this was using a somewhat convoluted setup, building a number
of things, not just derby. Building derby not directly but using ant from the command line,
but from another build file, using ant call to the 'all' target of the trunk's top level build.xml.
Properties are not set in ant.properties but are set in this "wrapper" build file.

I need to go and revamp that build setup - there's some cleanup that can be done / is necessary...

So it's ok.
However, I'd not like this change to get backported.


      was (Author: myrna):
    The difference was that after your change, it picked a Sun 1.6 instead of an IBM 1.6 jvm.

The environment where I saw this was using a omewhat convoluted setup, building a number of
things, not just derby. Building derby not directly but using ant from the command line, but
from another build file, using ant call to the 'all' target of the trunk's top level build.xml.
Properties are not set in ant.properties but are set in this "wrapper" build file.

I need to go and revamp that build setup - there's some cleanup that can be done / is necessary...

So it's ok.
However, I'd not like this change to get backported.

  
> 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