Bug 548819 - Lot of problems while setting Jre name
Summary: Lot of problems while setting Jre name
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.11   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: 2019-07-01 05:07 EDT by Vikas Chandra CLA
Modified: 2023-06-14 05:00 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vikas Chandra CLA 2019-07-01 05:07:44 EDT 
1) Once I reach the bin folder, name bin is selected and then when I go back to C:\eclipse\java13\openjdk-13-ea+24_windows-x64_bin\jdk-13 the name is not refresh.

2) If I update location to java-12, the name is not updated.
Comment 1 Eclipse Genie CLA 2019-07-01 05:09:18 EDT 
New Gerrit change created: https://git.eclipse.org/r/145208
Comment 2 Sarika Sinha CLA 2019-07-01 05:34:10 EDT 
Problem is genuine but we need to consider the impact on existing users and they might be used to this flow and we can not break the existing behavior without informing user. User might have given a name on purpose and system should not change that automatically. I see four options :
1. Have a "Refresh" button like we have for API Baseline new dialog.
2. If the JRE name is not empty, inform user.
3. Have a preference to specify if a name given by user can be overridden by system.
4. Disable JRE name field for "Edit".
Comment 3 Vikas Chandra CLA 2019-07-01 05:47:46 EDT 
>1. Have a "Refresh" button like we have for API Baseline new dialog.

I think the current way is better

2. If the JRE name is not empty, inform user.

That is a separate issue

3. Have a preference to specify if a name given by user can be overridden by system.

I think we should avoid giving too many preferences.

4. Disable JRE name field for "Edit".

I don't think disable is a good idea. However if  the user has manually edited  then possibly change of JRE name should not happen automatically.
Comment 4 Sarika Sinha CLA 2019-07-01 05:56:46 EDT 
(In reply to Vikas Chandra from comment #3)
> 
> I don't think disable is a good idea. However if  the user has manually
> edited  then possibly change of JRE name should not happen automatically.

Yes that's what we want, the options where to achieve this. A better solution is always welcome!
Comment 5 Eclipse Genie CLA 2021-06-21 15:56:23 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 6 Eclipse Genie CLA 2023-06-14 05:00:39 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.