> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 03, 2001 4:39 PM > To: [EMAIL PROTECTED] > Subject: Re: crimson 1.1 > > > Diane Holt <[EMAIL PROTECTED]> wrote: > > > Personally, I've never wanted any of the Ant stuff included in the > > classpath for my compiles -- but maybe other people do? > > The name is a little misleading, includeantruntime actually means > "include the CLASSPATH environment value". > > I usually want my javac tasks to use my CLASSPATH, unless I specify a > classpath explicitly that is.
mmm... a little bit dangerous to me because it may have side effects. (ie it may compile on your computer but not in the computer of someone else or more dangerous: compile differently and the build ends up with a Verify error). I want it to compile with the build information, not with the information available out of the build which may not be the same from one computer to another. I'm working on several modules on different versions (maintenance of course) and I think I'm not the only one so it is not very convenient to rely on the user classpath. A build is set for the project and that's it. All libs used are under source control and only those one should be used otherwise this is food for problems :( -- St�phane Bailliez Software Engineer, Paris - France iMediation - http://www.imediation.com Disclaimer: All the opinions expressed above are mine and not those from my company.
