[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: Cleaning the repository...

From: korebantic <korebantic_at_gmail.com>
Date: 2007-01-17 19:38:55 CET

> In most projects, folks don't even store compiled files in the first
> place (we ignore *.class in my Java web app, for example). The
> thinking is that if you have everything required to build the DLL
> stored in the repository, why are you redundantly storing the DLL?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
But what if your webapp is dependent on a third party jar? If you want to
preserve history, or rather make sure you have a repeatable build and
configuration of your software (and historical), wouldn't you want to put
external components in subversion?

This question ping-pongs in my mind, because another alternative would be to
use Maven to manage dependencies. However, even in this case IMO the whole
Maven concept of a dependency repository is nothing more than a dumbed down
version of a version control system.
Received on Wed Jan 17 19:39:24 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.