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

Bug 315102

Summary:

activating Applet Parameters tab makes configuration dirty

Product:

[Eclipse Project] JDT

Reporter:

Darin Wright <darin.eclipse>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

normal

Priority:

Version:

3.6

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

stalebug

Attachments:

Description	Flags
3.6 applet launch configuration file	none
3.5 applet launch configuration file	none

Description Darin Wright

2010-05-31 11:41:52 EDT

3.6 RC3

Steps:

* Create a workspace and an applet launch configuration in 3.5
* Open the workspace in 3.6
* Open the LCD
* As soon as the "Parameters" tab is activated, the "Apply" button becomes
enabled

Comment 1 Darin Wright

2010-05-31 12:07:47 EDT

In 3.6 comparing files, this additional attribute is present:

<mapAttribute key="org.eclipse.jdt.launching.APPLET_PARAMETERS"/>

Comment 2 Darin Wright

2010-05-31 12:09:33 EDT

Created attachment 170548 [details]
3.6 applet launch configuration file

Comment 3 Darin Wright

2010-05-31 12:10:04 EDT

Created attachment 170549 [details]
3.5 applet launch configuration file

Comment 4 Darin Wright

2010-05-31 12:31:49 EDT

This is not a migration issue. The problem is the "Parameters" tab. When applied, it stores the parameters map into the configuration (even if empty). However, the launch shortcut does not create an empty parameters map value.

Other steps:

* Create an Applet launch  with the launch shortcut (Run As > Java Applet)
* Open the LCD and go to the parameters tab

Comment 5 Eclipse Genie

2018-10-21 15:32:40 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.

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.