Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 22 Dec 2011 10:14:30 +0000 (UTC)
From: "Knut Anders Hatlen (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1712833952.38695.1324548870911.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-4845) Improve the dependency tracking for
 our build targets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-4845:
--------------------------------------

    Attachment: d4845-jsr169-nonoptional.diff

d4845-jsr169-nonoptional.diff addresses another issue in the build scripts. Earlier, the JSR-169 specific parts were optional, but now they're always built. However, the build scripts still model the old world, by compiling the mandatory parts first and the (previously) optional parts last. This adds to the complexity of the scripts, and also causes some redundancies (because some of the previously optional targets are now dependencies of the mandatory targets, but the optional targets are still invoked explicitly later in the build process).

The patch merges the optional targets with the non-optional ones, so that they get compiled in one go. It also removes the target that rewrites modules.properties for J2ME support, since that information could now be hard-coded in modules.properties.

I ran the regression tests successfully on both Java 6 and phoneME.
                
> Improve the dependency tracking for our build targets
> -----------------------------------------------------
>
>                 Key: DERBY-4845
>                 URL: https://issues.apache.org/jira/browse/DERBY-4845
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools
>    Affects Versions: 10.8.1.2
>            Reporter: Rick Hillegas
>         Attachments: check-build.ksh, d4845-buildbreak.diff, d4845-iapi-brokered-callable-stmt.diff, d4845-iapi-brokered-connection.diff, d4845-iapi-dependablefinder.diff, d4845-iapi-exception-util.diff, d4845-iapi-nodefactory-getnode.diff, d4845-iapi-readOnlyUpgrade.diff, d4845-iapi-resultsetstatistics.diff, d4845-iapi-slimmer-nodefactory.diff, d4845-iapi-statementnode.diff, d4845-iapi-stmt-isClosed.diff, d4845-iapi-unused-imports.diff, d4845-jsr169-nonoptional.diff, derby-4845-01-aa-removeParserPrep, derby-4845-02-aa-flipUtilsAndTypes.diff, tools-i18n.diff
>
>
> Derby is supposed to have an incremental build. That is, if you change a file, then the following command should recompile the file:
>    ant all
> There are several places in the graph of Derby build targets where this is not true. If you change a file in certain packages, a subsequent "ant all" won't notice the change. This issue is a place where we can track these bugs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira