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

["Darin Swanson" <Darin_Swanson@xxxxxxx>]

It appears that I have a "special" workspace that was causing a problem.
After creating a new workspace I can successfully use PDE selfhosting

Both Ant core and UI External Tools have a script folder containing a
buildExtraJAR.xml file.
These scripts update the extra classpath entries used by Ant.
In External Tools, the script buildSelfHostingJARs.xml runs both of these
scripts.
After updating the JARs, launch a target workspace using the Runtime
workbench launch configuration.
Run / test ant as required.

If anyone else has problems "self-hosting" to test / verify Ant changes
please annotate
http://bugs.eclipse.org/bugs/show_bug.cgi?id=24269

Thanks
Darins



                                                                                                                                                
                      Darin Swanson                                                                                                             
                                               To:      platform-ant-dev@xxxxxxxxxxx                                                            
                      09/30/02 02:19           cc:                                                                                              
                      PM                       Subject: Testing Ant in a target workspace                                                       
                                                                                                                                                
                                                                                                                                                



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