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

Bug 315103

Summary: JUnit configuration from shortcut is dirty in LCD
Product: [Eclipse Project] JDT Reporter: Darin Wright <darin.eclipse>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: markus.kell.r
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
3.6 launch file
none
3.5 launch file none

Description Darin Wright CLA 2010-05-31 11:45:35 EDT 
3.6 RC3

Steps:

* Create a new workspace using Eclipse 3.5
* Create a standard JUnit project with example tests
* Create a launch configuration for a test with a specific method
* (In my example, I created a test for "VectorTest.testClone()" using the "Run As > JUnit Test" launch shortcut.
* Open the workspace in 3.6
* Open the LCD
* As soon as the "Arguments" tab is activated, the "Apply" button becomes
enabled
Comment 1 Darin Wright CLA 2010-05-31 12:15:20 EDT 
In 3.6 the following attribute is missing from the config:

<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value=""/>
Comment 2 Darin Wright CLA 2010-05-31 12:15:41 EDT 
Created attachment 170553 [details]
3.6 launch file
Comment 3 Darin Wright CLA 2010-05-31 12:16:06 EDT 
Created attachment 170554 [details]
3.5 launch file
Comment 4 Darin Wright CLA 2010-05-31 12:37:26 EDT 
This is not a migration issue. The "Arguments" tab writes an empty value for arguments when apply is pressed for empty values (not sure why an empty value is written, as the code seems to be accounting for this).

Other steps:

* Create a Junit test using "Run As > Junit Test"
* Open the LCD on the configuration - the config is dirty immediately
Comment 5 Eclipse Genie CLA 2020-03-29 05:40:34 EDT 
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.