On Tue, Mar 11, 2008 at 2:29 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote: > > > For example, the jspwiki project currently under apache incubation > > stores its dependencies in the version-control system and will not > > change. And they are not stupid people; it is just the way they like to > > work. > > The core problem is one of disk space - storing artifacts in source > control means that there is no way to ever recover the artifacts used > should you want to clean out and archive old versions. > But then you would be breaking the old builds and bye-bye reproducibility! I don't see anyone purging repo1.maven.org anytime soon. I agree for a SNAPSHOT repository, using a SVN backing store is a "bad thing" For a release repository, using a SVN backing store is not that bad, as only the metadata changes > > Usually getting the development teams to explain their "store artifacts > in source control" position to the people who provide the budget for the > disk space usually solves this problem. > > Regards, > Graham > -- >
