Oops... Few days ago I got into an half amusing / half disappoining situation. I was working with a small piece of Java Open Source, at work, under Windows. It included some .bat files (along with the corresponding Unix .sh) to build and install the application. Well, only if that worked...
One of the .bat files included this line of code:
if %USE_JDK6%=="true" set ANT_OPTS=%ANT_OPTS% -Djava.endorsed.dirs=%ANT_HOME%\endorsed
Well, that line of code won't work as expected, and even more, if %USE_JDK6% is empty (wich happened quite often) the linne would completely crash. Let's better do it the righ way:
if "%USE_JDK6%"=="true" set ANT_OPTS=%ANT_OPTS% -Djava.endorsed.dirs=%ANT_HOME%\endorsed
For this and may other issues, the .bat file did not worked at all, and I had to spend some time doing some simple fixing. So I finally get to the point that probably nobody had tested this .bat file at all. Ouch!... I cound understand why and I could accept it, but including a faulty build environment for one platform is quite annoying. (And I felt like grumping a little bit about it over here).
(I have noticed that in newer versions of that software package this .bat and .sh files are happily gone, well, less trouble).
