File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes IDEs, Version Control and other tools and the fly likes Eclipse build path library not being updated Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "Eclipse build path library not being updated" Watch "Eclipse build path library not being updated" New topic
Author

Eclipse build path library not being updated

Melinda Savoy
Ranch Hand

Joined: Jun 21, 2005
Posts: 387

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.


Melinda Savoy
Ranch Hand

Joined: Jun 21, 2005
Posts: 387

Does anyone know if this is a bug in this version, 6.0.18, of Eclipse?
Jesper de Jong
Java Cowboy
Saloon Keeper

Joined: Aug 16, 2005
Posts: 14338
    
  22

Version 6.0.18 of Eclipse? That's strange. The latest version of Eclipse is 3.7.1.

6.0.18 sounds like a version number of Tomcat.


Java Beginners FAQ - JavaRanch SCJP FAQ - The Java Tutorial - Java SE 8 API documentation
Paul Clapham
Bartender

Joined: Oct 14, 2005
Posts: 18879
    
    8

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.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Eclipse build path library not being updated