----- Original Message ----- From: "Jose Alberto Fernandez" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 12:11 PM Subject: Re: [Bug 7153] - Need additional Microsoft Visual SourceSafe Tasks
>> Surely you don't need the bits that you can't compile, do you? Note that I don't believe most committers can compile >> all of Ant, either. Why not just compile the bits you need and use just those? >If it were just for my personal use, I would do it. But this is the version used by a large project. >>It is already a concern that we are using Alpha due to patches needed for <ejbjar> and the like. >If then I have to change the version of ANT everytime someone decides to use some additional task >that is going to be a problem. I prefer a nightly build from GUMP that at least has all the parts >(or as much as possible in there). Jose Alberto, didnt you see the bit in 'ant in ager' that talks about how to do this: you should be keeping the copy you are happy with under SCM; fetching from CVS and rebuilding as and when you see fit -and not before. there is no need to redist a nightly build on a daily basis, nor any need for >1 person to get and build the source. the reason for doing it locally is that there will always be changes with your version and the ant version. Why, even us committers often do that, working with something for a while till we are happy enough to share it. >Whould it be possible for ANT to tell which parts are off, something like > > ant -version > Apache Ant version 1.5alpha compiled on March 10 2002 > Missing modules: > this > this > and that > >Then at least one would know what is not there. Just a thought. I've already listed this as an RFE; I think it would be nice. you could iterate through all tasks and try and create them, then list available and unavailable -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
