Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <772276148.1212566985163.JavaMail.jira@brutus>
Date: Wed, 4 Jun 2008 01:09:45 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3703) Make it possible to build the JSR169
 support with the jdk1.4 libraries
In-Reply-To: <1298306616.1212449145198.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602218#action_12602218 ] 

Knut Anders Hatlen commented on DERBY-3703:
-------------------------------------------

Good points, Dan.

So, since Harmony is an Apache project, could we just do "svn copy" of
the relevant interfaces into our source tree and strip them down? Or
is there a more complex procedure? Much of the Harmony code has been
donated by a third-party. Does that mean we need to track down who the
copyright holders are and update our NOTICE file?

I don't think the fake interfaces increase the potential for
introducing errors, as I also suggested that the real JSR-169
interfaces are used if jsr169compile.classpath is set, just like
today. The only difference from the current state is that those who
haven't set jsr169compile.classpath also compile in JSR-169 support,
though with less compile-time checking than those who have set the
property.

I agree that stripping down the Harmony interfaces is better as it
also gives compile-time checking for those who haven't set the
property. So if it's not considerably more work, that sounds like the
way to go.

> 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.