Bug 6037 - JarPackageFragmentRoot.getUnderlyingResource() always returns null
Summary: JarPackageFragmentRoot.getUnderlyingResource() always returns null
Status: RESOLVED DUPLICATE of bug 6865
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows 2000
: P4 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-17 05:05 EST by Vladimir Grishchenko CLA
Modified: 2002-01-11 09:22 EST (History)
0 users

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 Vladimir Grishchenko CLA 2001-11-17 05:05:39 EST 
Unable to retrieve a reference to an IResource for a Java project library 
defined via internal (in-workspace) jar archive. The following returns null:

IClassFile.getParent().getParent().getUnderlyingResource()

This behavior is understood for external (out-of-workspace) libraries, but for 
internal ones it should be possible to retrieve a reference to undelying 
resource.
Comment 1 Vladimir Grishchenko CLA 2001-11-18 00:30:34 EST 
Closing since cannot reproduce it anymore.
Comment 2 Vladimir Grishchenko CLA 2001-11-18 00:31:30 EST 
Closing since cannot reproduce it anymore.
Comment 3 Vladimir Grishchenko CLA 2001-11-18 01:20:42 EST 
The problem is intermittent and "seems" to be related to the order of accesing 
internal/external libraries.
Comment 4 Philipe Mulet CLA 2001-12-13 10:16:36 EST 
We think we have isolated the pattern. It can occur when some code previously 
opened a JAR package fragment root in the wrong context (using a handle 
containing the wrong project). Even this package fragment root does not exist, 
its information is cached, and fooling all subsequent queries against elements 
inside it (they will incorrectly think they are located inside the original 
wrong project).

This defect is being resolved by revisiting the existency/opening condition of 
a JAR package fragment root (will be released in next integration build).

*** This bug has been marked as a duplicate of 6865 ***