Bug 240346

Summary: [build path] Variable Extension dialog should only render known archives as archives
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Bug Depends on: 229036    
Bug Blocks:    

Description Markus Keller CLA 2008-07-10 11:06:45 EDT
I20080617-2000

The 'Variable Extension' dialog (e.g. build path dialog > Add Variable... > Extends...) should only render known archives as archives. Currently, it also renders e.g. *.pdf and *.txt files with the 'Jar-of-binaries' icon.
Comment 1 Markus Keller CLA 2008-07-10 11:14:14 EDT
See also bug 229038 and bug 229042.
Comment 2 Dani Megert CLA 2008-07-10 12:03:00 EDT
Looks ugly but not critical for 3.4.x. Most users won't even see this because they won't alter the filter.

Time permitting for 3.5. Should be fixed together with the other two mentioned bugs.
Comment 3 Markus Keller CLA 2008-07-10 12:18:32 EDT
I think we should remove the filtered tree from the 'Add Jars', ... dialogs
again, and instead add a link in the relevant dialogs to allow the user to
configure a global pattern (bug 229036) for valid archives (default:
'*.jar,*.zip').

Then, the dialog could again render all matching files with a Jar icon.

Not sure yet where to put the preference (e.g. on Preferences > Java Build
Path?).
Comment 4 Eclipse Genie CLA 2019-02-11 14:10:32 EST
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 5 Eclipse Genie CLA 2021-02-02 06:59:41 EST
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-02-26 19:31:55 EST
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.