[DERBY-5479] Don't run MessageVetter unless messages have changed

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.9.1.0
• Fix Version/s: 10.9.1.0
• Component/s: Build tools
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 25/Oct/11 12:02
• Updated: 24/Jul/12 17:26
• Resolved: 26/Oct/11 07:57

Description

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.