Jump to: navigation, search

Difference between revisions of "ATF/Workspace"

< ATF
Line 3: Line 3:
 
To get a working workspace:
 
To get a working workspace:
  
1. Get an Eclipse 3.5 SDK
+
1. Get an Eclipse 3.5 SDK.
 +
 
 
2. Configure your Target Platform to additionally include several packages from Orbit and from Mozilla.
 
2. Configure your Target Platform to additionally include several packages from Orbit and from Mozilla.
 
* Download org.apache.xerces, org.mozilla.javascript from Orbit
 
* Download org.apache.xerces, org.mozilla.javascript from Orbit

Revision as of 08:26, 16 July 2009

ATF 0.3

To get a working workspace:

1. Get an Eclipse 3.5 SDK.

2. Configure your Target Platform to additionally include several packages from Orbit and from Mozilla.

3. Check out all ATF plug-ins together with their dependencies using the Team Project Set file attached to bug #283506.


ATF 0.2.3

To get a working wokspace:

1. Get an Eclipse 3.3 SDK

  • This gives you the basic eclipse environment that does not come with the ATF all-in-one

2. Install the ATF all-in one in that Eclipse environment

  • The ATF all-in-one contains the dependencies on Mozilla plugins (XULRunner, JavaXPCOM, etc). Its "all stuff you need to add on to Eclipse to get ATF".

3. If working with the source for Milestone 4 download the Team Set for Milestone 4

  • This source will re-build the Ajax-Toolkit plugins that are part of the ATF all-in-one package, but not the Mozilla plugins. It overlays the all-in-one with new code from CVS.

4. To get the intial code for eval debugging download the Team Set for Eval Debugging

The HEAD is going up changes that will changes the required new plugins. When the changes are complete a team_set for the head will be made available.