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] [Updated] (DERBY-3484) build fails if compile.classpath is set to the same value as jsr169compile.classpath
Date Wed, 02 May 2012 20:14:49 GMT

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

Myrna van Lunteren updated DERBY-3484:
--------------------------------------

    Assignee:     (was: Daniel John Debrunner)

I suspect Dan's not working on this. Unassigning.
Does this issue still make sense based on the current (10.9 alpha) build mechanism?
                
> 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

        

Mime
View raw message