Bug 477504 - Investigate calls to JavaProject.getPackageFragmentRoot(IResource) following bug 396854
Summary: Investigate calls to JavaProject.getPackageFragmentRoot(IResource) following ...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-15 15:49 EDT by Stephan Herrmann CLA
Modified: 2022-11-08 19:20 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 Stephan Herrmann CLA 2015-09-15 15:49:20 EDT 
Follow-up from bug 396854:

That bug changed one occurrence of
  project.getPackageFragmentRoot((IResource)target);
to
  project.getPackageFragmentRoot((IResource)target, this.rootPath);

which seamlessly extends the fix from bug 182537.

Inspecting the change I wonder if other calls of the same method may need the same addition, too.

First candidates after incomplete scanning:
- call inside DeltaProcessor.RootInfo.getPackageFragmentRoot(IResource)
  (just a few lines before the change from bug 396854)
- call inside JavaProject.computePackageFragmentRoots(IClasspathEntry, ObjectVector, HashSet, IClasspathEntry, boolean, Map)

etc.
Comment 1 Manoj N Palat CLA 2018-05-16 01:38:26 EDT 
Bulk move out of 4.8
Comment 2 Eclipse Genie CLA 2020-06-19 14:20:37 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 2022-11-08 19:20:31 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.