Mark Eggers wrote: > David, > > > Hmm, how can you tell that it is not using > > Forrest's packaged Ant? > > Without taking $ANT_HOME and $ANT_HOME/bin out of my > environment: > > C:\src\sites-src\resolver-test>ant -version > Apache Ant version 1.6.5 compiled on June 2 2005 > C:\src\sites-src\resolver-test>%FORREST_HOME%\tools\ant\bin\ant > -version > Apache Ant version 1.6.5 compiled on June 2 2005 > C:\src\sites-src\resolver-test> > > After taking $ANT_HOME and $ANT_HOME/bin out of my > environment: > > C:\src\sites-src\resolver-test>C:\Ant\bin\ant -version > Apache Ant version 1.6.5 compiled on June 2 2005 > C:\src\sites-src\resolver-test>%FORREST_HOME%\tools\ant\bin\ant > -version > Apache Ant version 1.6.5 compiled on May 16 2006 > C:\src\sites-src\resolver-test> > > Notice the compile dates. > > This works the same way in Cygwin.
Ah, i think that this is a separate issue. When we run 'forrest' i.e. $FORREST_HOME/bin/forrest[.bat] it clears ANT_HOME then calls $FORREST_HOME/tools/ant/bin/ant This makes it use Forrest's own Ant rather than any other Ant on the system. So calls like 'forrest validate-xdocs' will use Forrest's own Ant. However doing stuff with developing plugins, e.g. cd your-favourite-plugin edit something $FORREST_HOME/tools/ant/bin/ant local-deploy ... This skips the unsetting of ANT_HOME and uses whatever other Ant it finds on the system. So i think that we need to modify tools/ant/bin/ant to force it to use our Ant. -David
