[
https://issues.apache.org/jira/browse/DERBY-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602390#action_12602390
]
Knut Anders Hatlen commented on DERBY-3703:
-------------------------------------------
Hi Rick,
Both (1) and (2) sound reasonable to me. If we first write the code for the
interfaces, I think we should have the source, not the binaries, in the
repository. Creating dummy interfaces for the entire Foundation Profile API
sounds doesn't sound worthwhile, given that most of the classes that we compile
against don't contain any code anyway.
About the directories: java/build is already taken as a source root, so I don't
think they should be placed as subdirs of that directory. What about
java/stubs/jsr169/... ?
> 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.
