commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim O'Brien" <tobr...@discursive.com>
Subject RE: [all] Instead of source and binary - one distribution
Date Sat, 05 Jun 2004 02:20:26 GMT
 

> -----Original Message-----
> From: Martin Cooper [mailto:martinc@apache.org] 
> Sent: Friday, June 04, 2004 4:45 PM
> To: Jakarta Commons Developers List
> Subject: RE: [all] Instead of source and binary - one distribution
> 
> 
> 
> > -----Original Message-----
> > From: David Graham [mailto:grahamdavid1980@yahoo.com]
> > Sent: Friday, June 04, 2004 2:34 PM
> > To: Jakarta Commons Developers List
> > Subject: Re: [all] Instead of source and binary - one distribution
> >
> >
> >
> > --- Tim O'Brien <tobrien@discursive.com> wrote:
> > > We make releases both source and binary, but why not just start 
> > > cutting one release?  I can understand why a product like HTTPD 
> > > would be distributed without source, but the commons community 
> > > consists of developers.
> > >
> > > Can anyone think of any good reason to preserve the 
> current release 
> > > structure.
> >
> > Even though we distribute to developers, most of them 
> probably don't 
> > care about the source.  They care about adding the jar to their 
> > project and looking at the javadocs.  I just downloaded 
> codec for use 
> > in one of my projects and would have immmediately thrown away the 
> > source if it was included.  IMO, it's a waste of Apache's 
> bandwidth to 
> > distribute files users are just going to delete.
> 
> +1. I am firmly against throwing everything into a single 
> distribution.
> 
> I thought we just had this discussion a few weeks ago, anyway...
> 

Alright, issue is put to bed, sorry for the duplication.

Tim



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message