On 1/17/07, korebantic <korebantic@gmail.com> wrote:
>
>
> > 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?
> >
> >
>
> 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?
3rd-party JARs I do version, because I don't build them myself - I
don't have everything required to build them in my repository, so it
wouldn't be covered by my little rule above.
One could also use a vendor branch (and that JAR vendor's source), I
suppose, to build those components. But for my project, all I need or
want to deal with is the JAR shipped by the vendor.
For anything that I build from my own sources, I don't version the
compiled classfiles.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 17 19:53:05 2007