[
https://issues.apache.org/jira/browse/DERBY-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601984#action_12601984
]
Daniel John Debrunner commented on DERBY-3703:
----------------------------------------------
I'm somewhat dubious of creating fake interfaces for JSR 169, especially when
it's just as easy to create valid jsr 169 interfaces classes for ResultSet,
PreparedStatement & CallableStatement by copying the Harmony classes and
removing the methods that are JDBC 3.0 only.
The fake interfaces has the potential for changes to introduce errors where the
classes no longer fulfill then JSR169 interfaces.
> Make it possible to build the JSR169 support with the jdk1.4 libraries
> ----------------------------------------------------------------------
>
> Key: DERBY-3703
> URL: https://issues.apache.org/jira/browse/DERBY-3703
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Rick Hillegas
> Attachments: derby-3703-01-aa-moveJdbc3methods.diff,
> derby-3703-01-aa-moveJdbc3methods.diff
>
>
> It would be good to simplify the Derby build so that the whole product could
> be built out-of-the-box just from what's checked into the Derby repository.
> As a step toward this goal, it would be good to be able to build the jsr169
> support without having to download proprietary libraries.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
