This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In my web app workspace I have 7 projects that reference the Apache Tomcat lib directory (C:\server\Tomcat 6.0\lib), in each project's buildpath. I updated 1 of the jars in the tomcat lib directory but when I go to the .class file in the jar that I updated via Eclipse IDE I still see the old version of the class file.
I can go directly to the file system and view the class file in my updated jar and confirmed that it has the updated class file. So I'm not sue why Eclipse is not showing the updated file. When debugging my code the OLD .class file comes up when I hit the breakpoint.
I've refreshed each project and did an individual build on each project but it's not updating the file referenced in Eclipse build path which is C:\server\tomcat 6.0.
Any suggestions on how to remedy my problem would be appreciated. BTW, my version of Eclipse is 6.0.18.
I found that when my project (X) had another project (Y) in its build path, then jars in that other project's (Y's) build path took precedence over jars in my project's (X's) build path. Drove me crazy for half a day when I was trying to test with different versions of JavaMail.