db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4845) Improve the dependency tracking for our build targets
Date Thu, 04 Nov 2010 16:41:45 GMT

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

Rick Hillegas updated DERBY-4845:

    Attachment: derby-4845-01-aa-removeParserPrep

Attaching derby-4845-01-aa-removeParserPrep.diff. This patch cleans up an asymmetry in the
generation of Derby's grammars. Committed at subversion revision 1031069.

This patch should fix certain situations in which you see the following:

1) You build the codeline from scratch.

2) But the build dies on a compile-time error.

3) You fix the compile-time error and try "ant all" without doing a clobber, hoping for an
incremental finish to the interrupted build.

4) But now the build dies on unsatisfied references in the generated grammars.

Touches the following files:


M      java/tools/org/apache/derby/impl/tools/build.xml

Make the tools build depend on generation of the ij grammar the same way that the sql interpreter
build depends on generation of the sql grammar.


M      build.xml

Stop generating the grammars before they are really needed.

> 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
>            Reporter: Rick Hillegas
>         Attachments: check-build.ksh, derby-4845-01-aa-removeParserPrep, 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.
You can reply to this email to add a comment to the issue online.

View raw message