I suggest using Apache Continuum instead: http://maven.apache.org/continuum/.
It's very well done, extremally easy to set up and configure (web interface).
We've been using it for our projects here and I can really recommend it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It'd be pretty cool to make wala.eclipse.tests run on CruiseControl. Thanks for the suggestion and the link to the document on running a headless Eclipse and test automation. My initial attempt at running the example wasn't so successful (it has trouble to automatically fetch code from the repository) but I'll look into it more deeply this weekend.
BTW, are all the other WALA tests set up to run on Cruise Control now? What is the command to fetch WALA code from the HEAD of SVN? I may need that later.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Our Windows CC server is currently hosed, I plan to put up another one soon.
I've been running WALA in a headless Eclipse instance lately, and fixed up the code to compute analysis scopes for Eclipse projects. See the 'HeadlessWALA' launcher I checked in.
Adam: regarding CC vs Continuum; we've been using CC for years. The main limitation has been lack of support for distributed build farms, although Julian claims there has been some improvement recently. The startup cost for CC is sometimes a bit high, but we've already done that. CC seems to have a nicer web interface for JUnit results. Is there a particular feature of Continuum you like better than CC? Have you used it for distributed build farms?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Internally, we need a distributed build becuase we have a whole lot of tests and projects to run.
I know the CC server is not accessible outside IBM; it's a real pain to make a web server visible outside the IBM firewall, so I've been procrastinating.
Given that we've already done all the set up for CC, I don't see any strong motivation to switch to Continuum at the moment.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I think creating such a main is a plausible way to go. I'm not an Eclipse expert so there may be a better way; but this at least is one way forward.
SJF
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I found a way to launch Eclipse outside Eclipse, both as an Eclipse application and as a JUnit Plugin test! I'll show you below. It is tested on Eclipse 3.2.1 on a Windows XP. To make it run, you have change the paths to accomodate your Eclipse installation path and your workspace path.
1. ECLIPSE APPLICATION
* i.e., code in IPlatformRunnable; in this example, the code in com.ibm.wala.eclipse.headless.Main
* see also the Java launcher HeadlessWALAFromCommandLine
* java command (sorry for the verbose command!)
java -cp C:\eclipse3.2.1\eclipse\startup.jar org.eclipse.core.launcher.Main
-application com.ibm.wala.eclipse.HeadlessWALA -data C:\workspaces\20070310-wala/ -configuration file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/HeadlessWALA/ -dev file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/HeadlessWALA/dev.properties
-pdelaunch -nosplash
2. JUNIT PLUGIN TEST
* see also HeadlessWALAJUnitPluginTestsFromCommandLine
* java command (sorry for the verbose command!)
java -cp C:\eclipse3.2.1\eclipse\startup.jar org.eclipse.core.launcher.Main
-version 3 -port 3578 -testLoaderClass org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader -application org.eclipse.pde.junit.runtime.coretestapplication -product org.eclipse.sdk.ide -data C:\workspaces\20070310-wala/../runtime-walaWorkspace -configuration file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/pde-junit/ -dev file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/pde-junit/dev.properties -pdelaunch -os win32 -ws win32 -arch x86 -testpluginname com.ibm.wala.eclipse.tests -loaderpluginname org.eclipse.jdt.junit.runtime -classnames com.ibm.wala.eclipse.tests.WalaCGModelTest
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=403488
Originator: NO
I suggest using Apache Continuum instead: http://maven.apache.org/continuum/.
It's very well done, extremally easy to set up and configure (web interface).
We've been using it for our projects here and I can really recommend it.
Logged In: YES
user_id=1607199
Originator: NO
It'd be pretty cool to make wala.eclipse.tests run on CruiseControl. Thanks for the suggestion and the link to the document on running a headless Eclipse and test automation. My initial attempt at running the example wasn't so successful (it has trouble to automatically fetch code from the repository) but I'll look into it more deeply this weekend.
BTW, are all the other WALA tests set up to run on Cruise Control now? What is the command to fetch WALA code from the HEAD of SVN? I may need that later.
Logged In: YES
user_id=221724
Originator: YES
http://riverdale.watson.ibm.com:8080/cruisecontrol/ is our current CC server, running on linux.
Our Windows CC server is currently hosed, I plan to put up another one soon.
I've been running WALA in a headless Eclipse instance lately, and fixed up the code to compute analysis scopes for Eclipse projects. See the 'HeadlessWALA' launcher I checked in.
Adam: regarding CC vs Continuum; we've been using CC for years. The main limitation has been lack of support for distributed build farms, although Julian claims there has been some improvement recently. The startup cost for CC is sometimes a bit high, but we've already done that. CC seems to have a nicer web interface for JUnit results. Is there a particular feature of Continuum you like better than CC? Have you used it for distributed build farms?
Logged In: YES
user_id=403488
Originator: NO
Is distributed build required in this case?
What I like about continuum is that is's very easy to set up and manage, via a simple web-interface.
BTW, the build server is not accessible from the outside of IBM.
Logged In: YES
user_id=221724
Originator: YES
Internally, we need a distributed build becuase we have a whole lot of tests and projects to run.
I know the CC server is not accessible outside IBM; it's a real pain to make a web server visible outside the IBM firewall, so I've been procrastinating.
Given that we've already done all the set up for CC, I don't see any strong motivation to switch to Continuum at the moment.
Logged In: YES
user_id=1607199
Originator: NO
Steve,
I checked out your launcher. So, what we need is to run make a main for WALA eclipse test, and be able to run it on command line?
Logged In: YES
user_id=221724
Originator: YES
Annie,
Yes, I think creating such a main is a plausible way to go. I'm not an Eclipse expert so there may be a better way; but this at least is one way forward.
SJF
Logged In: YES
user_id=1607199
Originator: NO
I found a way to launch Eclipse outside Eclipse, both as an Eclipse application and as a JUnit Plugin test! I'll show you below. It is tested on Eclipse 3.2.1 on a Windows XP. To make it run, you have change the paths to accomodate your Eclipse installation path and your workspace path.
1. ECLIPSE APPLICATION
* i.e., code in IPlatformRunnable; in this example, the code in com.ibm.wala.eclipse.headless.Main
* see also the Java launcher HeadlessWALAFromCommandLine
* java command (sorry for the verbose command!)
java -cp C:\eclipse3.2.1\eclipse\startup.jar org.eclipse.core.launcher.Main
-application com.ibm.wala.eclipse.HeadlessWALA -data C:\workspaces\20070310-wala/ -configuration file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/HeadlessWALA/ -dev file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/HeadlessWALA/dev.properties
-pdelaunch -nosplash
2. JUNIT PLUGIN TEST
* see also HeadlessWALAJUnitPluginTestsFromCommandLine
* java command (sorry for the verbose command!)
java -cp C:\eclipse3.2.1\eclipse\startup.jar org.eclipse.core.launcher.Main
-version 3 -port 3578 -testLoaderClass org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestLoader -application org.eclipse.pde.junit.runtime.coretestapplication -product org.eclipse.sdk.ide -data C:\workspaces\20070310-wala/../runtime-walaWorkspace -configuration file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/pde-junit/ -dev file:C:/workspaces/20070310-wala/.metadata/.plugins/org.eclipse.pde.core/pde-junit/dev.properties -pdelaunch -os win32 -ws win32 -arch x86 -testpluginname com.ibm.wala.eclipse.tests -loaderpluginname org.eclipse.jdt.junit.runtime -classnames com.ibm.wala.eclipse.tests.WalaCGModelTest