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

Re: SVN as CMS

From: Nick Stolwijk <nick.stolwijk_at_gmail.com>
Date: Fri, 20 Mar 2009 17:31:25 +0100

IMHO, artifacts should never be version controlled. They are always
reproducible from your version control. To make it easier when you
lose the contents of your artifact repository[1], you could make a
backup of your artifact repository.

[1] I have a maven background, the artifact repository is the central
location where you store your artifacts, this could be a real
application, like Nexus, or just a simple filesystem, available
through a webserver.


Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem

On Fri, Mar 20, 2009 at 2:25 PM, <webpost_at_tigris.org> wrote:
> Hi All,
> Just curious to know if it is better idea to use SVN to store generate artifacts on building code. Up to now, i know that we should only use SVN for code and not for any library and artifacts.
> Could any one please comment/suggest on this.
> Thanks
> Pawan
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1364438
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-20 17:36:49 CET

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.