[
https://issues.apache.org/jira/browse/DERBY-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5474:
--------------------------------------
Attachment: d5474.diff
Attaching a patch that removes the fork attribute from the target so that it
uses the default value "no". It also removes the dir attribute, otherwise a
warning is printed about the property being ignored (since working directory
cannot be changed when fork is "no"). The tool doesn't use any relative path
names as far as I can see, so inheriting the working directory from the parent
process should be OK.
Additionally, it turns the initClientMessageIds() method into a static
initializer. This isn't strictly necessary, since initClientMessageIds() is
idempotent, but it saves a little bit of work when the main() method is invoked
multiple times in the same process.
> Speed up message splitting in build
> -----------------------------------
>
> Key: DERBY-5474
> URL: https://issues.apache.org/jira/browse/DERBY-5474
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.9.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
> Attachments: d5474.diff
>
>
> On a slow machine I sometimes use to build Derby, running the
> org.apache.derbyBuild.splitmessages tool takes 30 seconds and accounts for
> 15% of the total time needed to run "ant -q buildsource" (which builds the
> engine, the network server and the client, but not the tests or demos). The
> tool is invoked 15 times, and each time a new Java process is started because
> the Ant target has specified fork="yes". By changing it to run the
> splitmessages tool in the same Java process as the one running Ant, the time
> is reduced to 3-4 seconds on the same machine.
--
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
