Community
Participate
Working Groups
3.6 RC3. Similar to bug 315100, a JUnit Plug-in Test launch configration becomes dirty when migrated from 3.5 to 3.6 when the Plug-ins tab is activated. In addition, the configuration is dirty when the "Test" or "Main" tab is activated. Steps: * Create a workspace and JUnit Plug-in Tests launch configuration in 3.5 * I used "org.eclipse.jdt.debug.tests" as the plug-in to test, with a test class of "org.eclipse.jdt.debug.tests.AutomatedSuite" selected * Open the workspace in 3.6 * Open the LCD * As soon as the "Main" tab or "Test" tab is activated, the "Apply" button becomes enabled
The following additional attribute appears in 3.6: <stringAttribute key="org.eclipse.jdt.junit.TESTNAME" value=""/> As well, the same problem as bug 315100 happens (the following is added in 3.6): <booleanAttribute key="useCustomFeatures" value="false"/>
Created attachment 170555 [details] 3.6 launch file
Created attachment 170556 [details] 3.5 launch file
This bug is too out of date to be fixed.