[Subclipse-users] How to manage builds

I'm dealing with some libraries that I obtain from the developers' remote
Subversion repositories. Within Eclipse I therefore have both my application
project and the remote library's project grabbed out of Subversion. My
application depends on their libraries. (By the way, I'm using Java.)

What is the best practice regarding how to manage this dependency? Right now
I'm doing something that isn't as streamlined as I'm guessing some of you
have set up your development and build processes:

Everytime I do an "update" on the remote library to pull the latest updates
from the repository, I run the build.xml that comes with the remote library
that produces the package (JAR) from the source. Then in my project's
build.xml I copy their package (the JAR I just mentioned) into my
application's package (EAR) that will be deployed to the app server.

What I find inefficient about my current system is having to run two
build.xml files when the remote library is updated. This doesn't seem like
the most efficient process, and because I'm relatively new to all this I
don't understand how to avoid it: should I add that project's source folders
as source folders in my build path, add the whole project as a project in my
build path, or something else?

Any insight on how you do things would be really appreciated.

-- 
View this message in context: http://www.nabble.com/How-to-manage-builds-tf3202381.html#a8892281
Sent from the subclipse - users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org