-
Notifications
You must be signed in to change notification settings - Fork 0
Setup swarm.restclient in Eclipse
bugvish edited this page May 29, 2012
·
6 revisions
From a fresh Eclipse workspace, import the com.buglabs.bug.swarm.restclient. This can either be done via the git plugin or by using git on the commandline and importing the project from the filesystem.
The simplest approach is to use binaries for dependencies. This prevents the cascading project configuration issue when getting the workspace setup. We'll use PDE's build in mechanism for binary dependencies: the Target Platform configuration.
- Create a local folder for dependencies, say
~/swarm-libs
. - Download http://bugcommunity.com/swarm_libs/jackson-core-asl-1.9.2.jar into
~/swarm-libs
. - Download http://bugcommunity.com/swarm_libs/jackson-mapper-asl-1.9.2.jar into '~/swarm-libs'.
- Download http://bugcommunity.com/swarm_libs/org.touge.restclient.jar into
~/swarm-libs
. - In Eclipse, Preferences -> Target Platform -> Running Platform -> Edit -> Add.
- In the dialog select Directory and then
~/swarm-libs
. - The Target Content dialog should now show '3 plug-ins available' for
~/swarm-libs
. - Finish the dialog. The Touge and Jackson dependencies should now be resolved in the workspace projects.
- Create a JUnit launch configuration, run the ParticipationAPITests class. In the VM arguments text box add the test configuration:
-Dreport.misc=test.bugswarm.net,connector_test,3077514aa9aa5a5826cfd9d04ee059db1a18057d,7339d4a60c729308086341600d44c6424a4079cb,connector_test2,ddef1fa815d8549fa184e2716405f2cc553b5316,af9c58ce70d031934826bd9662f00420863e752b
- Launch the configuration. After a bit of time you should see the tests pass. The console output will show messages going to and coming from the swarm server.