Difference between revisions of "SWTBot/Dev Setup For Recorder Branch"

From Eclipsepedia

Jump to: navigation, search
(Initial version)
 
m (Dev Setup For Recorder Branch moved to SWTBot/Dev Setup For Recorder Branch: Moving in the right namespace)

Revision as of 21:47, 27 April 2010

Here are the instructions for setting up your development environment for the recorder branch.

  1. Download all projects from http://dev.eclipse.org/svnroot/technology/org.eclipse.swtbot/branches/recorder-spike
  2. Rename some resources as follows:
    • /org.eclipse.swtbot.eclipse.ui/META-INF/_MANIFEST.MF_eclipse_3_5 to /org.eclipse.swtbot.eclipse.ui/META-INF/MANIFEST.MF
    • /org.eclipse.swtbot.eclipse.ui/_build.properties.eclipse_3_5 to /org.eclipse.swtbot.eclipse.ui/build.properties
    • /org.eclipse.swtbot.eclipse.ui/_classpath.eclipse_3_5 to /org.eclipse.swtbot.eclipse.ui/.classpath
    • /org.eclipse.swtbot.junit4_x/META-INF/MANIFEST.MF_junit4_5 to /org.eclipse.swtbot.junit4_x/META-INF/MANIFEST.MF
    • /org.eclipse.swtbot.junit4_x/_classpath.junit4_5 to /org.eclipse.swtbot.junit4_x/.classpath
  3. Add all external plugins from /org.eclipse.swtbot.releng/externals/plugins to your target platform. One way to do that would be to create a target platform (Preferences > Plug-in Development > Target Platform) with all the plugins in your base eclipse install and the plugins from the path mentioned above.
  4. To run the recorder with a standalone application, start org.eclipse.swtbot.swt.recorder.ui.Main with the name of your standalone app as an argument. For example, you can use org.eclipse.swt.examples.controlexample.CustomControlExample as the argument.
  5. To run the recorder with an eclipse application, create an Eclipse Application launcher. Add the following code at an appropriate location where it will be called once.
Thread recorderThread = new Thread("SWTBotRecorder") {
			public void run() {
				new SWTBotRecorderWindow().createWindow();
			}
		};
		
		recorderThread.start();
  • You can set -Dorg.eclipse.swtbot.recorder.actions.print=true as a VM argument to make the recorder print to console as it records events.