Bug 522460 - [9] [search] splitpackagebinding bound search gives inexact match at times
Summary: [9] [search] splitpackagebinding bound search gives inexact match at times
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Manoj N Palat CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-19 00:08 EDT by Manoj N Palat CLA
Modified: 2023-01-29 06:56 EST (History)
2 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 Manoj N Palat CLA 2017-09-19 00:08:30 EDT 
follow-up of last part of bug 501162 comment 45

-- snip--
"On an additional note on the splitpackagebinding, JSB9T test 47, is still passing/failing on and off due to binding resolution - under investigation [have pulled the changes mentioned in bug 501162 comment 43 "
-- snip--
Comment 1 Manoj N Palat CLA 2018-08-16 00:30:18 EDT 
Bulk move out of 4.9
Comment 2 Eclipse Genie CLA 2020-09-13 17:28: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.
Comment 3 Eclipse Genie CLA 2023-01-29 06:56:28 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.