[DERBY-3484] build fails if compile.classpath is set to the same value as jsr169compile.classpath

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.2.0
• Fix Version/s: 10.5.1.1
• Component/s: Build tools
• Assignee: Daniel John Debrunner
• Reporter: Daniel John Debrunner
• Created: 29/Feb/08 18:51
• Updated: 17/Jun/13 09:19
• Resolved: 03/May/12 22:23

Description

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.

Issue Links

• relates to: DERBY-3984 Separate out the small number of build targets which really require JDK1.4 features from the bulk of the targets which ought to compile cleanly against small device libraries