Bug 538404 - Adding text to "VM arguments" field doesn't offer to Apply the changes
Summary: Adding text to "VM arguments" field doesn't offer to Apply the changes
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-29 20:13 EDT by David M. Karr CLA
Modified: 2022-10-15 12:54 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David M. Karr CLA 2018-08-29 20:13:36 EDT
I'm seeing a problem with run configurations in Photon that I've never seen before.

I often need to enter property settings in the "VM arguments" field in the run configuration and save those changes permanently.

Today, I'm seeing that when I enter text in that field, the "Apply" button doesn't ungrey.

I also tested making a change to the "Program arguments" field, and it does the same thing.

However, I was able to figure out a workaround. I found that the "Working directory" field does not have this problem. I tried changing it to "Other" and then entering the same value as the default. That made the Apply button sensitive. I then went up to the "VM arguments" field and entered the text I needed to add.

I then clicked Apply. When I ran my test, I verified that it was working, which means it was reading those additional properties I set.

This also demonstrates that not only was it not letting me apply the changes earlier, it actually wasn't even using them at all, because if I just clicked "Run", my test fails because those required properties are not set. I guess this last point is not that surprising.  If I can't click "Apply", it's not only not going to store it on disk, it's not going to apply them at all.

I looked in the log and I didn't see anything obviously related to this.
Comment 1 Sarika Sinha CLA 2018-08-30 05:46:13 EDT
Can you attach a simple java project and a launch configuration which is giving this error?
I am not able to reproduce using Eclipse SDK. Are you using plain SDK or you have additional plug-ins installed?
Comment 2 David M. Karr CLA 2018-08-30 19:17:49 EDT
I have many plugins, but I didn't see this in Oxygen, I'm certain of that.
Comment 3 Eclipse Genie CLA 2020-09-12 10:10:07 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.
Comment 4 Eclipse Genie CLA 2022-10-15 12:54:43 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.