|Re: eclipse.launcher returns NULL when running JUnit plug-in tests [message #986099 is a reply to message #986090]
||Sun, 18 November 2012 20:23
| Kivanc Muslu
Registered: November 2010
Stephan Herrmann wrote on Sun, 18 November 2012 12:57|
Possible workaround: explicitly pass this variable into your test launch?
Hi Stephan, I tried using the environment variables (in run configurations) tab to do this, however it did not work. I also tried to set the environment variable 'eclipse.launcher' using a @BeforeClass method. However, as far as I can see, the product (the second Eclipse with my plug-in running on it), is created and run way earlier than @BeforeClass method is executed. Since my plug-in tries to read 'eclipse.launcher', it still reads null and cannot spawn the headless (third) Eclipse.
Is there any other way that I can pass the variable and make sure that it is set before the second (i.e., testing Eclipse with my plug-in) is created?
Powered by FUDForum
. Page generated in 0.06529 seconds