Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315105

Summary: JUnit Plug-in Test launch configuration migration from 3.5 to 3.6
Product: [Eclipse Project] PDE Reporter: Darin Wright <darin.eclipse>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, markus.kell.r
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
3.6 launch file
none
3.5 launch file none

Description Darin Wright CLA 2010-05-31 11:49:57 EDT 
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
Comment 1 Darin Wright CLA 2010-05-31 12:17:55 EDT 
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"/>
Comment 2 Darin Wright CLA 2010-05-31 12:18:16 EDT 
Created attachment 170555 [details]
3.6 launch file
Comment 3 Darin Wright CLA 2010-05-31 12:19:17 EDT 
Created attachment 170556 [details]
3.5 launch file
Comment 4 Curtis Windatt CLA 2013-01-28 12:00:33 EST 
This bug is too out of date to be fixed.