我正在开发Eclipse插件，需要能够自动化构建和执行每个插件的测试套件（使用Junit）。测试在Eclipse内部工作，并且我可以像这里、这里、以及这里所描述的那样将插件拆分为实际的插件和用于单元测试的片段插件。然而，以上每种方法都存在同样的问题：发出构建或应该触发测试的Java ant任务/命令不会产生任何可观察到的副作用，并返回值“13”。我已经尝试了我能找到的所有方法，并且对Eclipse启动方式有了相当多的了解（例如：自从v3.3以来，你不能再使用startup.jar-- 它不存在了--但您应该使用org.eclipse.equinox.launcher）。不幸的是，虽然这显然是必要的信息，但远远不够。我正在使用Eclipse 3.4、Junit 4.3.1（org.junit4 bundle，但我更愿意使用JUnit 4.4。请参见这里）。那么，我的问题是：如何精确地自动化构建和测试Eclipse插件？编辑：为了澄清，我想使用类似ant + cruise control的东西，但我甚至无法在Eclipse之外完全运行单元测试。我说“类似”是因为还有其他技术可以实现相同的功能，如果这些技术能够使得此过程更加容易，我并不介意例如使用Maven或Buckminster等解决方案。编辑2：上面提到的“Java Result 13”似乎是由于找不到coretestrunner引起的。从日志中可以看出：
java.lang.RuntimeException: Application "org.eclipse.test.coretestapplication" could not be found in the registry. The applications available are: org.eclipse.equinox.app.error, com.rcpquickstart.helloworld.application.
at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:242)
at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
at org.eclipse.core.launcher.Main.main(Main.java:30)
!ENTRY org.eclipse.osgi 2 0 2008-11-04 21:02:10.514
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-11-04 21:02:10.515
!MESSAGE Bundle update@plugins/org.eclipse.test_3.2.0/ [34] was not resolved.
!SUBENTRY 2 org.eclipse.test 2 0 2008-11-04 21:02:10.516
!MESSAGE Missing required bundle org.apache.ant_0.0.0.
!SUBENTRY 2 org.eclipse.test 2 0 2008-11-04 21:02:10.516
!MESSAGE Missing required bundle org.eclipse.ui.ide.application_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2008-11-04 21:02:10.518
!MESSAGE Bundle update@plugins/org.eclipse.ant.optional.junit_3.2.100.jar [60] was not resolved.
!SUBENTRY 2 org.eclipse.ant.optional.junit 2 0 2008-11-04 21:02:10.519
!MESSAGE Missing host org.apache.ant_[1.6.5,2.0.0).
!SUBENTRY 2 org.eclipse.ant.optional.junit 2 0 2008-11-04 21:02:10.519
!MESSAGE Missing required bundle org.eclipse.core.runtime.compatibility_0.0.0.