> From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED] > Dominique Devienne wrote: > >FWIW, I've had at least 5 users having problems with the new Ant 1.6 > >launcher because they had unexpanded environment variables in their > >CLASSPATH. I can almost trace adoption of Ant 1.6 in this company just by > >questions about the IllegalArgumentException they're all getting. I > suspect > >this is not the last we here of this. --DD > Hi Dominique, > > I do not understand this issue of unexpanded environment variable in > one's CLASSPATH. > How do your colleagues set their CLASSPATH ? > Are they working under Windows or UNIX ?
Always on Windows (Win2K or WinXP), always with SUN's JDK 1.4.2. > For me, whatever the operating system, if your profile says : > export > CLASSPATH=$APPLICATIONA_HOME/classes:$APPLICATIONB_HOME/classes:$APPLICATI > ONC_HOME/first_jar > > or the equivalent under your operating system, by the time the CLASSPATH > environment variable reaches an application it is already expanded. > > I do not set CLASSPATH under Windows, but I set PATH with the system > applet of the control panel. I set PATH to be > %ANT_HOME%\bin;%JAVA_HOME%\bin ... > but when I open a shell window, the PATH is already expanded. Sure enough, unless one of the variable is mistyped or is not defined. Define in the control panel applet a CLASSPATH env. var which references other env. vars in its values, and these other env. vars are not defined and you end up in a DOS window with unexpanded variabled in the CLASSPATH. BUT, the unexpanded variable lead may be a dead end. The last user told me that what fixed it for him was to remove stuff added to the classpath by the Java Media Framework installer. The pity is that everytime I've asked for the classpath triggering the problem, the users had already changed it in the control panel applet, and can't recall the faulty classpath!!!! > How do your colleagues start ant : > - do they start one of the supplied scripts (ant.bat or ant for Unix), Always thru a local script called build.bat that ends in calling the official ant.bat. These build.bat scripts are minimal, and have not changed during the switch to Ant 1.6. It's unlikely they have anything to do with the problem. > - or do they start ant through an IDE, or somehow through API calls I'm talking about problems from the command line here exclusively. > - or do they start somehow java org.apache.tools.ant ... from the > command line ? If I get pinged again about this, I really try to get the classpath that triggers the problem. I tried to get it from the guy who reported a similar problem on the dev list, but could never get him to provide the right info :-( --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
