The problem with these is that the developer community never followed the code. I assume this is some political issue in Jakarta I'm not aware of.
As far as I know, the Commons idea is that the group who donate the code are seen as the ones who are the maintainers. The very concept of a 'Commons committer' is anathema to the Commons charter [although such a thing does evolve over time]. bzip/tar/zip ended up just sitting in Commons waiting for a developer community to arrive. There are a few things here, in decreasing importance: 1) Code must be maintained to be worth using. 2) Code must have a community to be maintained. 3) The same code ought not to live in more than one place. 4) Reusable code ought to be in Jakarta Commons. Now, if the Ant developers are the only ones doing 1), and they are the only 2) for the code, then according to 3) the code should be in one place. This place ought to be Jakarta Commons, but if this is not possible then it should be in Ant as 4) is the least important of the 4 things. So, +1 to the Ant guys managing the code inside Commons, +0 to the Ant guys offering the jars as a separate build. Hen On Thu, 23 Jan 2003, Nicola Ken Barozzi wrote: > > Forgot to cc here. > > -------- Original Message -------- > Subject: Bzip, tar, zip, etc > Date: Wed, 22 Jan 2003 18:10:47 +0100 > From: Nicola Ken Barozzi <[EMAIL PROTECTED]> > Reply-To: Avalon Developers List <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > Organization: Apache Software Foundation > To: Ant Developers List <[EMAIL PROTECTED]> > CC: Avalon Developers List <[EMAIL PROTECTED]> > > > Ant has packages for zip, bzip and tar stuff. Really? > Ok, I know you all know. ;-) > > The point is that some of these packages IIUC were copied in Avalon repo > as indipendent packages, and then since they were not in scope I put > them in commons sandbox, and now we are deprecating the avalon versions. > > Now, we have asked some time back, "why not let Ant use the commons > versions"? > > Gump... blah blah blah... bootstrap... blah blah blah... > > Now that they have been put in commons for some time, it's quite evident > that there, they are dead. > > So, the solution seems simply to make these separate jars and make them > available also separately from Ant. > > ant.jar > ant-zip.jar > ant-bzip.jar > ant-tar.jar > > Ant keeps them, they are maintained, and we get separate jars to use in > other projects. > > Comments? > > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
