Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 26 Oct 2011 07:59:32 +0000 (UTC)
From: "Knut Anders Hatlen (Resolved) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1660367060.17249.1319615972194.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1505437001.12943.1319544272148.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (DERBY-5479) Don't run MessageVetter unless
 messages have changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen resolved DERBY-5479.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: Patch Available)

Thanks, Rick! For now, I think I'll just go for the patch as it is. If too many files in the top-level generated directory becomes a problem, it should be easy enough to clean it up.

Committed revision 1189059.
                
> 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: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.9.0.0
>
>         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