At 04:02 3/4/01 +0100, Stephane Bailliez wrote: >> 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 :(
100% agree - been to through too many dll/library/jar hells to count and want ultra build guarentees if at all possible ... however not everyone feels that way ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
