You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2008/02/29 19:52:51 UTC
[jira] Created: (DERBY-3484) build fails if compile.classpath is
set to the same value as jsr169compile.classpath
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
Reporter: Daniel John Debrunner
Assignee: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3484) build fails if compile.classpath is
set to the same value as jsr169compile.classpath
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-3484:
----------------------------------
Component/s: Build tools
> 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
> Reporter: Daniel John Debrunner
> Assignee: 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.
-
You can reply to this email to add a comment to the issue online.