Bug 19071 - Refreshing jar files and Type Hierarchy view
Summary: Refreshing jar files and Type Hierarchy view
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: ---   Edit
Assignee: Erich Gamma CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-04 10:38 EDT by Andre Weinand CLA
Modified: 2002-09-05 11:00 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Weinand CLA 2002-06-04 10:38:03 EDT
- import JUnit into project as jar file
- open type hierarchy on TestCase
- outside of Eclipse delete a subclass of TestCase from jar file
- in type hierarchy view select TestCase (or the deleted class) and refresh 
with F5
Observe: for a brief moment the busy cursor appears. However the deleted class 
does not disappear.
- Select the deleted class
Observe: the missing icon (red square) appears for the input object of the 
other pane of the package viewer.

BTW: there is no Refresh action in the package viewers context menu. However a 
busy cursor appears when pressing F5.
Comment 1 Erich Gamma CLA 2002-06-04 13:20:45 EDT
1) there should be a refresh action in the context menu when a JAR is selected.
2) when JAR has changed I'd expect that we get a type hierarchy delta.
   checking with Philippe. If this isn't the case then we have to refresh the 
hierarchy manually.
Comment 2 Philipe Mulet CLA 2002-06-05 06:06:10 EDT
You don't get anything beyond a delta for the changed external JAR. Hierarchies 
should be refreshed then since we did not provide more information in the delta.
Comment 3 Erich Gamma CLA 2002-06-07 13:29:35 EDT
Shouldn't the ITypeHiearchyChangedListener be notified in this case? Then this 
would work for all type hierarchies and not only the ones shown in Views.
Comment 4 Philipe Mulet CLA 2002-06-10 06:14:53 EDT
Hierarchies should be fine since they already listen for Java element changes. 
In this case, they will see the JAR delta and react accordingly.

On a simple example, it did work fine when refreshing a JAR.
Comment 5 Dirk Baeumer CLA 2002-06-13 06:21:12 EDT
Needs to be tested again.
Comment 6 Erich Gamma CLA 2002-06-17 04:13:26 EDT
Adam pls verify
Comment 7 Adam Kiezun CLA 2002-09-05 08:37:44 EDT
it's fine - but only after you manuall do 'refresh' on the jar

back to inbox for closing if that's good enough
Comment 8 Dirk Baeumer CLA 2002-09-05 11:00:50 EDT
Refreshing the Jar is what the user has to do as long as we don't have file 
system listeners.