Sorry to post across the userlists.
I'm using Subversion, Ant, and Anthill OS to automate my projects. We
release many products in different projects.
Currently I have set up a property sheet in Anthill for each project's
build.xml and everything works fine. However, many of the projects create a
.jar file which is used or needed by other projects. I tell my build.xml
file in each project where to get the compiled jar files.
With so many jar files being copied all over and our projects growing larger
and larger daily, I was asked to create my own top parallel project and call
all the build files from my master proj and make this project the exchange
folder for all the jar files or any other artifact. It's a cleaner way, of
course and more contained but it entails more work on my part.
I've got my master build file to work, running at the cmnd prompt, however,
Anthill does not like it when you tell a build file to check out other top
level project files from the repo. Should I create dummy project files in
Anthill just to check out the other projects and then let my build file take
control?
Somebody please give me guidance on the big picture. Is this a good idea to
have a master and separate build project aware of all the other projects and
but the other projects not being aware of it? How do I bypass the Anthill's
shortcoming? By switching to CruiseControl? Are there or do you have any
examples I could see please?
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 5 23:52:12 2006