Distributed updates

I've been using subversion for months now to version sourcecode for my
company but now I'd like to use it for distributing updates. This
would be for a web application that runs in Weblogic 7 (like tomcat
only much more expensive).
Whenever my graphics boys edit a graphic for the web-based UI, they
have to recompile the .ear file in order to put their changes into
production.
Those of you who are administrators know why this is dangerous.
What I'd like to do instead is have changes to the application be
submitted to a repository and then have the post-commit script kick of
a reaction that recompiles the .ear and pushes it to the clients.

Now, I'm sure I could write one friggin monster bash or perl script to
handle this. But I'm sure I am not the only one to think up such a
setup.
Anyone ever heard of this before?

-- 
Regards,
Bryan Simmons
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 What is this "sleep" of which you speak?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org