Bug 262343 - Update EAR libraries should be integrated with Refresh action.
Summary: Update EAR libraries should be integrated with Refresh action.
Status: VERIFIED DUPLICATE of bug 255174
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M4   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-26 04:56 EST by Krzysztof Daniel CLA
Modified: 2010-12-07 05:13 EST (History)
5 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 Krzysztof Daniel CLA 2009-01-26 04:56:04 EST 
Due to following inconsistency:

1. Create user library with external jar in regular java project.
2. modify the path of the jar (make the library invalid)
3. invoke "refresh" /* compilation error appears */

1. create dynamic web project and add user library to it
2. modify the path of the jar (make the library invalid)
3. invoke "refresh" /* no compilation problems, in the preferences there is a problem indicator that something is wrong with the library */
4. invoke "Update EAR libraries" /* compilation error appears */
Comment 1 Carl Anderson CLA 2009-01-28 14:33:45 EST 
Christopher, what version of WTP is this for?  1.5.5?  3.0.3?  Assuming the latter, so I am targetting this to 3.0.5 (since 3.0.4 is shutting down.)
Comment 2 Jakub Jurkiewicz CLA 2009-02-11 11:09:45 EST 
After small investigation I think that it is not WTP issue, it looks more like issue with Project Explorer, as the Refresh action works in Package Explorer, but it doesn't work in Project Explorer (I cannot see any relation to WTP). 
I looked at the bugs reported against refresh in Project Explorer, but most of them are related to working sets and this problem looks different.
I suggest changing the summary of this bug to: "Refresh action in Project Explorer doesn't refresh the classpath" or something like this and set the component to Platform/UI.
Comment 3 Jakub Jurkiewicz CLA 2009-02-18 04:38:58 EST 
To clarify the scenerio to reproduce is following:
1. Create Java project
2. Add external jar to the build path
3. On the file system change the path to the jar
4 In the Project Explorer view choose Refresh on the project node -> no error appears

Note that ff refresh is invoked in the Package Explorer view and error appears.
Comment 4 Jacek Pospychala CLA 2009-02-23 06:25:37 EST 
Jason, could you have a look at this?
With Jakub we tend to think it's JDT issue.
Comment 5 Jacek Pospychala CLA 2009-03-13 05:38:23 EDT 
Dani,
is the scenario from comment 3 familiar to you?
Comment 6 Dani Megert CLA 2009-03-13 06:29:41 EDT 
Yep, this is bug 255174 in JDT Core. The Package Explorer works because its org.eclipse.jdt.ui.actions.RefreshAction does the additional work but it does not work doing the refresh in any other view (e.g. Navigator or Project Explorer) that provides its own Refresh action.
Comment 7 Dani Megert CLA 2009-03-13 06:30:02 EDT 

*** This bug has been marked as a duplicate of bug 255174 ***
Comment 8 Satyam Kandula CLA 2010-12-07 05:13:40 EST 
Verified for 3.7M4 using build I20101205-2000