You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2004/07/31 06:07:51 UTC
DO NOT REPLY [Bug 30422] New: -
[Patch] Mutual Exclusion Tasks
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30422>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30422
[Patch] Mutual Exclusion Tasks
Summary: [Patch] Mutual Exclusion Tasks
Product: Ant
Version: 1.6.2
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Core tasks
AssignedTo: dev@ant.apache.org
ReportedBy: dak@dotech.com
I've created 2 tasks <Wait> and <Notify>.
The use case is where you have parallel ants running (on some server) doing
builds, but 1 part of the build (in our case, some JFCUnit) needs to be single
threaded. By this I mean that each of the build/validates that we are doing can
run in parallel, with the exception of the JFCUnit portion due to focus
issues.
So, wrap the JFCUnit portion of the validate in the <Wait> <Notify> tasks. What
wait does is create a lock file, check for other locks, of none exist, it goes
forward. If other locks exist, it removes its lock file and does a random wait
(based on parameters) and tries again. <Notify> simply removes the lock.
I have a test build file and the working tasks if anyone wants to see and play
around.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org