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-6213) Deprecate support for Java 5 and CDC
Date Fri, 10 May 2013 07:01:20 GMT

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

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

After derby-6213-05-ab-misc2.diff I saw that a build job started failing when compiling SqlXmlUtil.java:

compile_types:
    [javac] Compiling 67 source files to /code/derby/trunk/classes
    [javac] /code/derby/trunk/java/engine/org/apache/derby/iapi/types/SqlXmlUtil.java:47:
error: package org.w3c.dom.xpath does not exist
    [javac] import org.w3c.dom.xpath.XPathEvaluator;
    [javac]                         ^
    [javac] /code/derby/trunk/java/engine/org/apache/derby/iapi/types/SqlXmlUtil.java:48:
error: package org.w3c.dom.xpath does not exist
    [javac] import org.w3c.dom.xpath.XPathExpression;
    [javac]                         ^
    [javac] /code/derby/trunk/java/engine/org/apache/derby/iapi/types/SqlXmlUtil.java:49:
error: package org.w3c.dom.xpath does not exist
    [javac] import org.w3c.dom.xpath.XPathResult;
    [javac]                         ^
(...)

This seems to happen only if I build with JDK 7, have j15lib set explicitly, and j16lib is
NOT set.

The patch in question removed the separate build target for SqlXmlUtil which put ${xmlApis}
on the class path when compiling this file. ${xmlApis} contains some interfaces that are not
part of the Java SE specification. The interfaces happen to be included in Oracle JDK 6 and
7 (and, I think, in OpenJDK and IBM's SDK as well), which is why it works when java16compile.classpath
is based on libraries from Java 6 or newer. But even if this particular build problem will
probably go away once PropertySetter is updated to ignore j15lib, we may want to reintroduce
the separate build target for SqlXmlUtil with ${xmlApis} on the class path in order to

a) make sure it compiles on JDK implementations that don't include the non-standard XML interfaces

b) make it less likely that dependencies on the non-standard interfaces creep into other classes
                
> Deprecate support for Java 5 and CDC
> ------------------------------------
>
>                 Key: DERBY-6213
>                 URL: https://issues.apache.org/jira/browse/DERBY-6213
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools, Documentation, Javadoc
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>         Attachments: derby-6213-01-aa-collapsePublishedAPI.diff, derby-6213-02-aa-org.apache.derby.vti.diff,
derby-6213-03-aa-misc.diff, derby-6213-03-ab-misc.diff, derby-6213-04-aa-vtiPackageOnJava7.diff,
derby-6213-05-ab-misc2.diff, derby-6213-06-aa-convertProductToJava6.diff
>
>
> The developer community has approved the proposal to sunset support for Java 5 and CDC:
http://apache-database.10148.n7.nabble.com/VOTE-Sunsetting-support-for-Java-5-and-CDC-td129832.html#a129925
> This issue tracks a number of tasks needed to implement this proposal:
> I) Remove build support for Java 5 and CDC.
> II) Purge user doc references to Java 5, CDC, and the JDBC 4 DataSources.
> III) Remove the JDBC 4 version of the public api from the published javadoc. The recently
introduced CP2 DataSources would need to migrate to the JDBC 3 version of the published javadoc.
The JDBC 4 versions of the DataSources would still exist, but they would be vacuous extensions
of their JDBC 3 counterparts.
> IV) On the wiki, document our expectation that maintenance releases will support the
same platforms as the original feature release cut from their branch.
> V) Decide what to do with the SimpleMobileApp. Probably we want to just remove this demo
since its purpose is to show how to run Derby on the deprecated CDC platform.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message