[
https://issues.apache.org/jira/browse/DERBY-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267300#comment-13267300
]
Knut Anders Hatlen commented on DERBY-3484:
-------------------------------------------
I think it still makes sense, but it looks like build.xml on trunk already sets
compile.classpath to jsr169compile.classpath:
<!--
The lowest common denominator compile path for Derby. We expect that
the bulk of the Derby product will run on small device platforms
(CDC/FP 1.1).
-->
<property name="compile.classpath" value="${jsr169compile.classpath}"/>
It was changed in DERBY-3984. It's probably OK to close this bug now.
> build fails if compile.classpath is set to the same value as
> jsr169compile.classpath
> ------------------------------------------------------------------------------------
>
> Key: DERBY-3484
> URL: https://issues.apache.org/jira/browse/DERBY-3484
> Project: Derby
> Issue Type: Bug
> Components: Build tools
> Affects Versions: 10.2.2.0
> Reporter: Daniel John Debrunner
> Priority: Minor
>
> Allowing compile.classpath to be set to jsr169compile.classpath is to ensure
> that the mainstream code that is build (using compile.classpath) does not
> depend on classes outside the currently supported J2ME/CDC/Foundation 1.1
> level.
> This was to avoid methods not in J2ME/CDC/Foundation 1.1 creeping into the
> code, as in DERBY-2109.
> Fails currently in the shared code accessing JDBC XA and ParameterMetaData
> classes. Used to work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
