Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <536166429.1229968964407.JavaMail.jira@brutus>
Date: Mon, 22 Dec 2008 10:02:44 -0800 (PST)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Issue Comment Edited: (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
In-Reply-To: <196390229.1228925084392.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-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658605#action_12658605 ] 

myrna edited comment on DERBY-3984 at 12/22/08 10:02 AM:
----------------------------------------------------------------------

This patch is based on the first attempt at check-in for DERBY-3988...Could you please update it ?
The patch didn't apply cleanly to the current trunk (although it only had a problem with trunk/build.xml...and I was able to change that quite easily manually, or I could apply to revision 727106, but  I'd like us to be on the same level).

      was (Author: myrna):
    This patch is based on the first attempt at check-in for DERBY-3988...Could you please update it ?
The patch didn't apply cleanly to the current trunk (although it only had a problem with build.xml...and I was able to change that quite easily manually, or I could apply to revision 727106, but  I'd like us to be on the same level).
  
> 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
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3984
>                 URL: https://issues.apache.org/jira/browse/DERBY-3984
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-3984-01-aa-defaultToJsr169.diff
>
>
> It would be good to make jsr169 the default platform for most Derby build targets. This will allow the build to raise compile-time errors when a checkin violates the small-device contract. Only a small number of features (listed in DERBY-3966) really require JDK1.4. Something like the following may work:
> 1) Finish up DERBY-3966 so that java4compile.classpath defaults to an approximation of ${jdk14xmlSupport}: ${java15compile.classpath}
> 2) Make compile.classpath default to jsr169compile.classpath
> 3) Fortunately, jsr169compile.classpath itself already defaults to ${jsr169stubs}:${java14compile.classpath}
> 4) Change a (hopefully) small number of targets to use java14compile.classpath rather than compile.classpath

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.