Community
Participate
Working Groups
Example: 1.) Create Junit test 2.) Run it 3.) Go to launch configuration and add a paramter, e.g. -os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} -consoleLog -lars true Press the Show command line button: C:\Program Files\Eclipse Foundation\jdk-11.0.12.7-hotspot\bin\javaw.exe -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:63817 -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Declipse.pde.launch=true "-Declipse.p2.data.area=@config.dir\p2" --add-modules=ALL-SYSTEM -Dfile.encoding=Cp1252 -classpath "C:\Users\vogella\Downloads\eclipse-SDK-I20220110-0550-win32-x86_64\eclipse\plugins\org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar" org.eclipse.equinox.launcher.Main -os win32 -ws win32 -arch x86_64 -nl de_DE -consoleLog -lars true -version 3 -port 63816 -testLoaderClass org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader -loaderpluginname org.eclipse.jdt.junit4.runtime -classNames Test -application org.eclipse.pde.junit.runtime.uitestapplication -product org.eclipse.sdk.ide -data "C:\Users\vogella\workspace\content/../junit-workspace" -configuration file:C:/Users/vogella/workspace/content/.metadata/.plugins/org.eclipse.pde.core/pde-junit/ -dev file:C:/Users/vogella/workspace/content/.metadata/.plugins/org.eclipse.pde.core/pde-junit/dev.properties -os win32 -ws win32 -arch x86_64 -nl de_DE -consoleLog -lars true -testpluginname a
JUnit tests launching and configuration is in the scope of JDT UI.
(In reply to Lars Vogel from comment #0) > Example: > > 1.) Create Junit test > 2.) Run it > 3.) Go to launch configuration and add a paramter, e.g. > > -os ${target.os} -ws ${target.ws} -arch ${target.arch} -nl ${target.nl} > -consoleLog -lars true > > Press the Show command line button: > > C:\Program Files\Eclipse Foundation\jdk-11.0.12.7-hotspot\bin\javaw.exe > -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:63817 > -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true > -Declipse.pde.launch=true "-Declipse.p2.data.area=@config.dir\p2" > --add-modules=ALL-SYSTEM > -Dfile.encoding=Cp1252 > -classpath > "C:\Users\vogella\Downloads\eclipse-SDK-I20220110-0550-win32- > x86_64\eclipse\plugins\org.eclipse.equinox.launcher_1.6.400.v20210924-0641. > jar" org.eclipse.equinox.launcher.Main > -os win32 > -ws win32 > -arch x86_64 > -nl de_DE > -consoleLog > -lars true > -version 3 > -port 63816 > -testLoaderClass org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader > -loaderpluginname org.eclipse.jdt.junit4.runtime > -classNames Test > -application org.eclipse.pde.junit.runtime.uitestapplication > -product org.eclipse.sdk.ide > -data "C:\Users\vogella\workspace\content/../junit-workspace" > -configuration > file:C:/Users/vogella/workspace/content/.metadata/.plugins/org.eclipse.pde. > core/pde-junit/ > -dev > file:C:/Users/vogella/workspace/content/.metadata/.plugins/org.eclipse.pde. > core/pde-junit/dev.properties > -os win32 > -ws win32 > -arch x86_64 > -nl de_DE > -consoleLog > -lars true > -testpluginname a I have not been able to reproduce this issue. Can you please provide a screen shots of your launch configuration dialog where the parameter is added.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
