Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 11431 invoked from network); 21 Apr 2006 16:43:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Apr 2006 16:43:07 -0000 Received: (qmail 75257 invoked by uid 500); 21 Apr 2006 16:43:05 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 75204 invoked by uid 500); 21 Apr 2006 16:43:04 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 75193 invoked by uid 99); 21 Apr 2006 16:43:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 09:43:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates 64.233.166.179 as permitted sender) Received: from [64.233.166.179] (HELO pproxy.gmail.com) (64.233.166.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Apr 2006 09:43:03 -0700 Received: by pproxy.gmail.com with SMTP id f28so495279pyf for ; Fri, 21 Apr 2006 09:42:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TekCE1+Zd9UP2rSfNae1EaKbjyejqtR4hFdjsAJBmC+ZBhelW72TKVAQZVF2P7cbs1qeqCKrYF/CF6q44tXRY30HEjRK3EUXhQx4oASATBcXzqauYZBdZiUsNRurkwy580y9wCtSYEhwsBp08/MxBjAxvc60F1Pt6X4iHLxvjto= Received: by 10.35.54.20 with SMTP id g20mr59009pyk; Fri, 21 Apr 2006 09:42:41 -0700 (PDT) Received: by 10.35.22.15 with HTTP; Fri, 21 Apr 2006 09:42:41 -0700 (PDT) Message-ID: <31cc37360604210942u6b684110o11d96bacdd1098d7@mail.gmail.com> Date: Fri, 21 Apr 2006 09:42:41 -0700 From: "Henri Yandell" To: repository@apache.org Subject: Re: Repo complaints In-Reply-To: <1a5b6c410604142330g7fd2b3c1k728199fd9b10e0d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <31cc37360604141038le77a7edo72e8fb0fbd745cfe@mail.gmail.com> <1a5b6c410604141209r61d76bccsc9bcfd4a78225d4f@mail.gmail.com> <31cc37360604141928k68056ba1k97ddb95b72984908@mail.gmail.com> <1a5b6c410604142330g7fd2b3c1k728199fd9b10e0d9@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 4/14/06, Carlos Sanchez wrote: > On 4/14/06, Henri Yandell wrote: > > Any reason not to just rm the distribution folders? > > nope I'll look into doing so. > > On the commons-lang source/javadoc - how do the projects replace the > > ones currently deployed? Can we deploy to the m1 repository on apache > > and it'll replace, or will the ones that are there by hand take > > precedence? > > new ones will replace old ones (I think). We'll need to check after. > > > > > How do you build them out of interest? Source distribution, svn tag? I > > noticed that they don't have a manifest (I presume you used zip rather > > than jar?), is there a need for a manifest? > > they only use case for them I know is IDE integration, so as long as > it's a valid jar it's ok. You can do either from tag or source distro Reason for asking in this case is that until very recently the tag for Lang 2.1 was broken - it had source that shouldn't be in it. I'm guessing you used the distro or did it after the tag was fixed as you've not got the text package in there. Hen