ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephane Bailliez <>
Subject RE: [Bug 7153] - Need additional Microsoft Visual SourceSafe Ta sks
Date Tue, 19 Mar 2002 10:09:00 GMT
> -----Original Message-----
> From: Nigel Magnay []
> Indeed - I thought, given the documentation on the site, that 
> the correct
> way to submit patches was to the developers list, with 
> [PATCH] on the front.
> Is this wrong? I can see that many other people are doing the 
> same thing. 

It can happen indeed but there are lots of traffic in ant mailing list so
chances are that it will be lost in the traffic whereas it won't be in

> True. Its also frustrating to look through the logs to find 
> that someone has
> created an enhancement that you were thinking of doing or 
> need, but that
> nobody did anything with it so it's possibly stale with respect to the
> current source tree. Yes I could do a custom build but it's a 
> huge pain in the bum!

> Concrete example:
> That would have been really useful to me.

Maybe, but then I'm not sure you realize about the problems of maintaining
these tasks. That's a huge problem and it has been discussed before, as a
user you would like all the tools you are using at time t to be available.
I'm a user as well that what I want. :)
As a committer you receive the aggregation of all the tools users are using
at moment t. That's a lot and you have to make choice whether or not this is
important or not.

Your example is actually a good one especially since it is a commercial
product. I will have to do the maintenance for all versions forever because
I must take care of backward compatibility. See JUnit and JavaCC. There are
probably others and that's what I will have to do as well for JProbe 4.0 to
be released which has a different layout structure from 2.x/3.x.

Now multiply by the number of products out there that users 'use' and just
imagine the complexity if we had to maintain code for all versions of all
A good example would have been for example the VAJ tasks which as noted by
Jon were not compiling for more than 3 months but not a committer did have
the API at hands. What about testing things for example for weblogic 5.x and
6.x, Clearcase, VSS, Starteam, etc...

I'm sorry this is impossible to deal with dependency explosion.

So we have to make choice. Hard for some people, I agree.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message