db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6856) Make it possible to build Derby using JDK 9
Date Sun, 08 May 2016 20:12:12 GMT

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

Rick Hillegas updated DERBY-6856:
    Attachment: derby-6856-04-ab-autoboxingDeprecationWarnings-part2.diff

Attaching derby-6856-04-ab-autoboxingDeprecationWarnings-part2.diff. This second rev of the
patch corrects a mistake which caused a boatload of errors. I am re-running the tests to see
if there are any additional errors after correcting this mistake.

In the following routine in SQLSmallint...

	public Object	getObject() 
		if (isNull())
			return null;
	      return new Integer(value);

...I changed the last line to...

			return value;

That was wrong because of the JDBC asymmetry that Integer is the JDBC object type for primitive
short. The value field has type short. I have corrected this as follows...

          return (int) value;

> Make it possible to build Derby using JDK 9
> -------------------------------------------
>                 Key: DERBY-6856
>                 URL: https://issues.apache.org/jira/browse/DERBY-6856
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Rick Hillegas
>         Attachments: derby-6856-01-ab-addShardingKey.diff, derby-6856-01-ac-cleanup.diff,
derby-6856-02-aa-addShardingKey.diff, derby-6856-03-aa-autoboxingDeprecationWarnings.diff,
derby-6856-03-ab-autoboxingDeprecationWarnings.diff, derby-6856-04-aa-autoboxingDeprecationWarnings-part2.diff,
> Derby can't be built with JDK 9. Java 9 introduces new JDBC classes like java.sql.ShardingKey
and methods which refer to these new classes.
> In addition, project Jigsaw has created a new way to name classes (see http://openjdk.java.net/jeps/220).
This breaks the PropertySetter build tool which we use so that old JVMs can compile Derby
and so that Derby can be compiled to run on old JVMs.
> It is likely that we will need to leave this issue open throughout the development cycle
of Java 9.

This message was sent by Atlassian JIRA

View raw message