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] [Resolved] (DERBY-3484) build fails if compile.classpath is set to the same value as jsr169compile.classpath
Date Thu, 03 May 2012 22:24:47 GMT

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

Myrna van Lunteren resolved DERBY-3484.

       Resolution: Fixed
    Fix Version/s:
         Assignee: Daniel John Debrunner

I'm marking this issue as fixed in 10.5 and assigning back to Dan, because commits are connected
to this issue - although as Knut remarked, more changes went in for DERBY-3984, fixed in 10.5.

> 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:
>            Reporter: Daniel John Debrunner
>            Assignee: Daniel John Debrunner
>            Priority: Minor
>             Fix For:
> 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
> 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


View raw message