Community
Participate
Working Groups
I have a project that has an external Jar file that is specified in the Java Build Path of my project properties. If I modify that external jar (change a method signature in a given class), eclipse does not see the change when I am editing a source file that depends on that change that I made in the external jar file. For example, 1) Say a have a project called Test. It has a reference to an external jar called foo.jar. 2) I have a class called DoSomething.java in my Test project that references a class in the foo.jar 3) If I change the method signature in the foo.jar that DoSomething.java is referencing then eclipse is not seeing the change in the foo.jar file. I tried to refresh and rebuild the project but it does not see the change. The only way to make the DoSomething.java class see the jar change is to get out of Eclipse all together and come back in.
Did you try to refresh the JAR by selecting it in the package explorer view and use the refresh action from the pop-up menu ? (not inside the navigator, in the package explorer view).
I have not tried doing a refresh from the package explorer. I would expect the Rebuild project to reload the references for the external jars.
Refreshing is expensive, we will only do so when asked to. We could add a mechanism for automatically performing it on build action, but this is likely going to slow down the build in general, just to check that nothing changed. Why is "refresh" a problem at all ? Isn't it what you do in the navigator already if you change some resource directly on the filesystem and want to have Eclipse see the changes ?
Ok to close?
[Your last response] Why is "refresh" a problem at all ? Isn't it what you do in the navigator already if you change some resource directly on the filesystem and want to have Eclipse see the changes ? That is what I am saying, a refresh on my source java file will not see the change that occurred in the jar file. The only way that I can get my source java file to see the change that occurred in the jar file is to shut down eclipse completely and start it back up. Am I missing something?
After thinking about it a little more, I believe that eclipse should not refresh the external jars when you refresh a given java source file but I DO think that external jars should be reloaded if you refresh the project itself.
But this is what happens if you perform a refresh action in the package explorer view. Not in the navigator. Aren't you seeing this behavior already ? Note that we could not hook the JAR refresh into the navigator (if we could we'd have done it). Please confirm whether it works or not.
If I refresh from within the Package viewer then it works as it should. It would be nice if the refresh worked within the Navigator view but as you explained in your previous post that is not possible. Sorry for all the confusion. I will refresh from the Packager viewer from now on.
Good, closing then.
