Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 2774 invoked from network); 12 Aug 2003 03:06:09 -0000 Received: from umbongo.flamefew.net (64.253.103.114) by daedalus.apache.org with SMTP; 12 Aug 2003 03:06:09 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id 0CD53C87; Mon, 11 Aug 2003 23:06:10 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id 08A21BDC for ; Mon, 11 Aug 2003 23:06:10 -0400 (EDT) Date: Mon, 11 Aug 2003 23:06:09 -0400 (EDT) From: Henri Yandell X-X-Sender: hen@umbongo.flamefew.net To: Jakarta Commons Developers List Subject: Re: [docs] Crappy build system In-Reply-To: <3F3857E5.1040508@mail.more.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 11 Aug 2003, Glenn Nielsen wrote: > Henri Yandell wrote: > > > > Ouch. The 1.7M Xerces jar is hurting my uplink :) > > > > Yeah, and that is one of many reasons not to put jars into CVS. So I should ask velocity for commit rights so I can remove it there? I have commit rights for jakarta-site2, so I can go ahead and remove things from there. Having the jar in CVS once is bad. Having it in N times makes no difference, so if we're going to have them in CVS I'd rather the system was a) simpler and b) stable. Although I've checked them in, I can rm them from the repo if need be. Another option would be to move the xdocs over to the jakarta-site2 module. Hen