Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: 68.142.198.213 is neither permitted nor
 denied by domain of mcintyre.a@gmail.com)
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <437B7515.9080807@bristowhill.com>
References: <54ac72d70511151720y749c8c0dp12298d31bf20d52d@mail.gmail.com>
 <437AB1D9.8060803@bristowhill.com>
 <D3DC5E3E-C8BC-4A68-A4AE-0748B08224A9@gmail.com>
 <437B54F6.7020602@bristowhill.com>
 <1881621A-69DB-49D5-9B85-F5A8C90C8A82@gmail.com>
 <437B7515.9080807@bristowhill.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4542658E-CF8C-4392-8A73-384AAA2DD6F2@gmail.com>
Content-Transfer-Encoding: 7bit
From: Andrew McIntyre <mcintyre.a@gmail.com>
Subject: Re: [doc] DITA-OT in Derby svn
Date: Wed, 16 Nov 2005 10:14:47 -0800
To: <derby-dev@db.apache.org>


On Nov 16, 2005, at 10:06 AM, Jean T. Anderson wrote:

> If we were just committing a jar file or two, like we do with the  
> jakarta-servlet jar for the derby code build, I wouldn't see any  
> problem at all with it. But by committing the entire software  
> distribution we're providing alternate distribution (in addition to  
> SourceForge), even if to just a small number of developers. It  
> would be as if we included the entire jakarta-servlet distribution,  
> which we don't do (lest I cause confusion) and wouldn't do.

Hmm, but we include the entire javacc and jakarta-oro distributions  
in the code tree, in tools/java. Should we not be doing that?

> My intuition says this wouldn't fly, but if you feel strongly about  
> it, I suggest you close the loop with infrastructure@.

The thing is that I *don't* feel strongly about it. :-)  If it's an  
issue, then we continue to point to Sourceforge.

> My preference would be to look into a tool that can automate the  
> software fetch, like maven does; and, in the meantime, instruct the  
> developers who want to build the derby DITA docs to download the  
> tool kit from SourceForge.

I'll look into maven, but in the interest of getting this going, I'll  
just commit everything mentioned in my previous mail but the toolkit  
zip.

andrew