db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5479) Don't run MessageVetter unless messages have changed
Date Tue, 25 Oct 2011 12:16:32 GMT

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

Knut Anders Hatlen updated DERBY-5479:

    Issue & fix info: Patch Available
> Don't run MessageVetter unless messages have changed
> ----------------------------------------------------
>                 Key: DERBY-5479
>                 URL: https://issues.apache.org/jira/browse/DERBY-5479
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d5479-1a.diff
> Continuing my series of patches micro-optimizing the build scripts...
> MessageVetter is always run as part of the build, also in incremental builds when nothing
has changed. Since it needs to go through more than 800 files, it may take a while (just half
a second on the fastest machine I tested, so not a big deal, but that's still a significant
portion of the total time in an incremental build). We should skip the message check in incremental
builds if none of the messages have changed.

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


View raw message