Running unit tests with buckminster 3.6 against 3.5 platform [message #512305] |
Thu, 04 February 2010 16:03 |
Carsten Reckord Messages: 139 Registered: July 2009 |
Senior Member |
|
|
Hi again,
After updating my buckminster installation from 3.5 to 3.6 and switching from the old googlecode version of the junit plugin to the official
buckminster one I am having trouble running my unit tests.
My target platform is still eclipse 3.5 and contains the 3.5 JDT plugins, including org.eclipse.jdt.junit4.runtime_1.1.0, org.junit_3.8.2
and org.junit4_4.5.0. My test fragments depend on org.junit4 >= 4.3.1. Finally, the launch configuration has
<launchConfiguration type="org.eclipse.pde.ui.JunitLaunchConfig">
....
<booleanAttribute key="default" value="true"/>
<stringAttribute key="application" value="org.eclipse.pde.junit.runtime.coretestapplication"/ >
<stringAttribute key="org.eclipse.jdt.junit.TEST_KIND" value="org.eclipse.jdt.junit.loader.junit4"/>
....
</launchConfiguration>
With this setup, running the tests from within a normal eclipse 3.6M5 works just fine. But with buckminster headless I get
!ENTRY org.eclipse.osgi 2 0 2010-02-04 12:53:14.829
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-02-04 12:53:14.830
!MESSAGE Bundle reference:file:/home/hudson/tools/buckminster/plugins/org.ec lipse.jdt.junit4.runtime_1.1.100.v20100124-2000.jar was not
resolved.
!SUBENTRY 2 org.eclipse.jdt.junit4.runtime 2 0 2010-02-04 12:53:14.830
!MESSAGE Missing required bundle org.junit_4.7.0.
I can't really see where the difference is between the working eclipse install and the "broken" buckminster. The jdt and pdt junit runtimes
and org.junit plugins are all the same, as are workspace and target platform.
|
|
|
Re: Running unit tests with buckminster 3.6 against 3.5 platform [message #512355 is a reply to message #512305] |
Thu, 04 February 2010 13:34 |
Carsten Reckord Messages: 139 Registered: July 2009 |
Senior Member |
|
|
Sorry, found my stupid mistake by myself.
My test fragments did not have a dependency on org.eclipse.jdt.junit4.runtime and so the target platform in the headless build was missing
the 3.5 version of it, therefore getting the 3.6 one from buckminster, which lead to the problem.
On 04.02.2010 17:03, Carsten Reckord wrote:
> Hi again,
>
> After updating my buckminster installation from 3.5 to 3.6 and switching from the old googlecode version of the junit plugin to the official
> buckminster one I am having trouble running my unit tests.
>
> My target platform is still eclipse 3.5 and contains the 3.5 JDT plugins, including org.eclipse.jdt.junit4.runtime_1.1.0, org.junit_3.8.2
> and org.junit4_4.5.0. My test fragments depend on org.junit4 >= 4.3.1. Finally, the launch configuration has
>
> <launchConfiguration type="org.eclipse.pde.ui.JunitLaunchConfig">
> ...
> <booleanAttribute key="default" value="true"/>
> <stringAttribute key="application" value="org.eclipse.pde.junit.runtime.coretestapplication"/ >
> <stringAttribute key="org.eclipse.jdt.junit.TEST_KIND" value="org.eclipse.jdt.junit.loader.junit4"/>
> ...
> </launchConfiguration>
>
> With this setup, running the tests from within a normal eclipse 3.6M5 works just fine. But with buckminster headless I get
>
> !ENTRY org.eclipse.osgi 2 0 2010-02-04 12:53:14.829
> !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2010-02-04 12:53:14.830
> !MESSAGE Bundle reference:file:/home/hudson/tools/buckminster/plugins/org.ec lipse.jdt.junit4.runtime_1.1.100.v20100124-2000.jar was not
> resolved.
> !SUBENTRY 2 org.eclipse.jdt.junit4.runtime 2 0 2010-02-04 12:53:14.830
> !MESSAGE Missing required bundle org.junit_4.7.0.
>
> I can't really see where the difference is between the working eclipse install and the "broken" buckminster. The jdt and pdt junit runtimes
> and org.junit plugins are all the same, as are workspace and target platform.
|
|
|
Powered by
FUDForum. Page generated in 0.04121 seconds