Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334782 - [Dialogs] Invalid return of Open Resource
Summary: [Dialogs] Invalid return of Open Resource
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 08:53 EST by Fabrício Pereira CLA
Modified: 2019-09-24 13:49 EDT (History)
3 users (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 Fabrício Pereira CLA 2011-01-19 08:53:41 EST 
Build Identifier: 20100917-0705

I found by "Roubo*VO.java" and it returns these two resources:
RouboFurtoNovo.java
RouboFurtoNovoDAO.java

And this last is invalid.

Reproducible: Always

Steps to Reproduce:
1.Open the "Open Resource"
2.Type "Roubo*VO.java"
3.Verify the return invalid
Comment 1 Paul Webster CLA 2011-01-19 08:59:35 EST 
Why is the last one invalid?  Was it added by a tool through auto-generation?  Was it deleted from the workspace by a program outside of eclipse?

PW
Comment 2 Remy Suen CLA 2011-01-19 09:02:10 EST 
As far as I know, case sensitivity is no longer a concern when you insert asterisks.
Comment 3 Oleg Besedin CLA 2011-01-19 09:46:02 EST 
I think it works as expected. To force "tails" to match, add "<" character:

Open resource dialog
Type 
   Roubo*Vo<

The file matching in those dialogs has some interesting logic, see the help topic 

Workbench User Guide > Reference > User interface information > Search > "Open Resource"

for some examples. Its loosely based on regular expressions but has a number of additions.
Comment 4 Lars Vogel CLA 2019-09-24 13:49: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.