Community
Participate
Working Groups
1. overwrite a jar file in your file system 2. right-clic in the tree node which represents the jar file ==> you can't select "Refresh From Local" you have to : 3. delete the link to the jar (right-clic / Delete). 4. open the project properties window (right-clic / Properties). 5. add the jar as an external jar. 6. close the project properties window. and you can't : 3. open the project properties window (right-clic / Properties). 4. remove the jar. 5. add the jar as an external jar. 6. close the project properties window. ==> no update
external JARs are unmanaged resources hence refresh from local doesn't work. adding and remove in the UI doesn't work since the JavaCore doesn't see the difference. the only other workaround that comes to mind is to close and reopen project. adding a refresh button for external JARs on the build path property page would be another option, but there is no JDT Core API to refresh a build path entry. Moving to JDT Core for comment.
changed version to 2.0
We would need some way to be notified that the user performed a 'refresh from local', and update all external JAR references. A separate mechanism wouldn't be intuitive.
If adding such a refresh entry functionality, would you call it upon refresh from local ?
Will a fix make it into 2.0?
Conference call with customer tomorrow on this issue. Can someone please comment on the current status of this issue? Additional test data regarding this has also been provided: Additional testing appears to show that the source attachment is not refreshed in WSAD but the actual code is. The code changes are picked up at runtime but changes to the source of the class are not visible when the class is opened to the editor. In my testing, this scenario occurs if the jar file is referenced as a jar file or an external jar file.
pls see 16091
*** This bug has been marked as a duplicate of 16091 ***