I have a very pragmatic solution to this problem. Include a reference to the contrib stuff in both the resources and FAQ sections of the ANT documentation. Someone has already mentioned that it is in the FAQ of the website, but I didn't check that because I had already checked the FAQ that came with the download. If it is put in a prominent place where newbies can easily find it, it will no doubt save them a lot of time, and would have saved me a lot of time.
Now I have a question for you Steve: You said you don't have much need for conditionality apart from <fail>. This is exactly what I want to use it for, but there is no conditionality built into fail either. So how do you do it? > From: Steve Loughran <[EMAIL PROTECTED]> > Subject: "if" task > Date: Tue, 30 Apr 2002 11:20:37 -0700 > Content-Type: text/plain; > charset="iso-8859-1" > > ----- Original Message ----- > From: "Gordon Tyler" <[EMAIL PROTECTED]> > To: "Ant Users List" <[EMAIL PROTECTED]> > Sent: Tuesday, April 30, 2002 10:01 AM > Subject: Re: "if" task > > > > I'll add another annoying me too message to this thread. > > > > We have a fairly complex Ant build script (just under 1000 lines, not > > counting external properties files and a separate 300 line bootstrap > nightly > > build.xml) and it would be so much better with foreach and if tasks. > > I'm -0 on if/then; ok with try/catch > > Maybe as a former prolog programmer it makes more sense to me, but I dont > have too many needs for conditionality apart from <fail>, even doing complex > deployment stuff. What we have right now is a reasonable conceptual model, > and too much <if><then>, <for>, gets in the way of doing the stuff in a > significantly better way. > > > > > Yes, we could use the contrib tasks but there is some internal resistance > to > > using non-core tasks and I don't have much say in what goes into our CVS > > controlled version of Ant. So having them in the core set of tasks would > be > > preferable. > > I am afraid you need to deal with your internal resistance...and you dont > need to put the tasks into ant_home\lib, just use a classpath on <taskdef> > and load them from a jar local to your project. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
