Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of mfncooper@gmail.com designates
 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=EkYWS1JiZ0H2JuD6QZp7SqXLYQ3AkO/wXyPIlbVOPcNGPBu6GB8XOgda2v54xGgfUqllf7ua2uoCisd/ihXM4p6IRS6vmhoQG5DS6eGPfkIEAEPAPVdyYKOy8XIgWVQFGtKRzwifgF6qAYQEKwzS0vuqjvHaYPC4PbEYC/DY7Yk=
Message-ID: <16d6c6200701062107m2f196833je24a48ac55a2ff7b@mail.gmail.com>
Date: Sat, 6 Jan 2007 21:07:44 -0800
From: "Martin Cooper" <martinc@apache.org>
Sender: mfncooper@gmail.com
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [all] jarfiles in svn
In-Reply-To: <1168145943.9310.23.camel@blackbox>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_44071_28604210.1168146464150"
References: <1168145943.9310.23.camel@blackbox>

------=_Part_44071_28604210.1168146464150
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 1/6/07, Simon Kitching <skitching@apache.org> wrote:
>
> Hi,
>
> I noticed (due to a recent commit message) that commons-transaction has
> jarfiles checked in to svn, eg
>
> http://svn.apache.org/repos/asf/jakarta/commons/proper/transaction/trunk/lib/
>
> What's the general policy on this? Sorry if this has been discussed
> before; I don't remember it.


It has been discussed before, but it's been a while since it's come up. The
general consensus has been "don't do it". There are lots of reasons to avoid
doing this, and no good reasons to do so, especially since we're using Maven
now.

Personally, I really really dislike jarfiles in the version control
> system. For a start, if every project were to do this, the impact on the
> Apache SVN repository would be huge.


Yep. I'm with you on both points.

I would instead prefer to see ant builds using "get" to download jars as
> needed. The maven repositories can be used as a convenient source for
> the jars, eg
>
> http://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk/build.xml


Right, and an Ant build generated by Maven will in fact get the dependencies
from the Maven repo, just as Maven does.

--
Martin Cooper


BTW, note that there is *no* way to remove a file from SVN once it is
> committed short of a repo dump/restore (which is a major effort on a
> repo the size of Apache). A "svnadmin obliterate" command is about the
> oldest outstanding feature request...
>
> Regards,
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

------=_Part_44071_28604210.1168146464150--