On Tue, 11 Jun 2002, Remy Maucherat wrote: > > But you broke the ant download as > > http://jakarta.apache.org/builds/jakarta-commons/release/commons-logging/v1.0.1/ > > does not exist yet. > > > > Getting commons-logging from cvs and building it is not very dificult > > and is probably better that having a jar file in the repository. > > This can be done in the meantime. Or we can also try to get > commons-logging 1.0.1 out ASAP. Costin, what do you think ?
The current solution of using 'released' versions will create problems, what happens with commons-logging now is just one example. We should be able to patch/fix the software we depend on. Assuming that the stars will allign when we want to release and 20 or so software packages will have a release at the same time ( or shortly before ) is crazy. Assuming 20 or so software packages are bug free and don't need any fix and will work just fine is also a bit too optimistic. I'm not saying we should use HEAD, but the 'stable' branch of each component we depend on, where fixes are made. Anyway, that's my opinion of what it 'should'. The reality is that it's much easier to use either .jars in CVS or download some packages. I have updated the j-t-c/lib with builds from latest ( I suppose the commit message was too big so filtered out ), and I'll check in a file that'll build most of the stuff from source. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
