[platform-ant-dev] Testing Ant in a target workspace

["Darin Swanson" <Darin_Swanson@xxxxxxx>]

I thought I would share how I am currently testing Ant changes.

I set up a "testing Ant" Eclipse installation (full Eclipse installation of
the latest build)

There are two scripts that I use. Both are called updateTarget.xml and live
in the scripts directories of org.eclipse.ant.core and
org.eclipse.ui.externaltools.
This scripts are available via CVS for these two projects.
As well in org.eclipse.ui.externaltools/scripts there is updateTargets.xml
which runs both scripts.
These scripts generate the plugins for org.eclipse.ant.core and
org.eclipse.ui.externaltools and copy them to the "testing Ant" Eclipse
installation.

To use the update scripts as defined in the scripts directories of
org.eclipse.ant.core and org.eclipse.ui.externaltools, the "testing Ant"
 Eclipse installation will need to be placed in a directory structure
of:../../Debugger/Ant/
Of course you can modify the scripts as you would like.

I then launch the "testing Ant" Eclipse installation in "attach" debug
mode:
C:\Debugger\Ant\eclipse\eclipse.exe -vm c:
\jdk1.4.1_b15\jdk1.4.1\jre\bin\java.exe -debug -data c:
\workspacesAntTesting -showlocation -vmargs -Xdebug -Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000.
If you do not plan to do any debugging you can launch the testing Ant
Eclipse any way you like.

From my development workspace, I create a remote Java Application launch
configuration and I use this to debug any problems.

So my normal work flow:
      make all of the changes to fix the current problem
      run updateTargets.xml
      Fire up the "testing Ant" Eclipse
      Ensure that the problem is fixed.

Please let me know if you have any problems with this explanation ;-)
Darins