Bug 175183 - Jars in library not recognized sometimes.
Summary: Jars in library not recognized sometimes.
Status: RESOLVED DUPLICATE of bug 154984
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 critical with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Maxime Daniel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-22 15:26 EST by Falk Langhammer CLA
Modified: 2007-03-13 06:01 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Falk Langhammer CLA 2007-02-22 15:26:11 EST
+++ This bug was initially created as a clone of Bug #154984 +++

-- Original description start --
Sometimes after a restart of eclipse/ clean build, Jars in added libraries are not recognised and this results in compilation error. To solve the problem, I have to remove the library assignment to the project, build the project and add the project again. Occurs in Win2k and WinXP
-- Original description end --

This bug bites many people, incl. us.
You may Google for "unbound classpath container" or similiar, e.g. http://dev.eclipse.org/newslists/news.eclipse.tools.jdt/msg16305.html and you will see that this bug exists since a while and still persists.

It seems to almost always emerge in real-world size projects while not being reproducible easily in toy projects. Our workspace is 150MB and cannot be attached, contains 7 dependent projects incl. WST and we almost stopped using Eclipse because of this. No other IDE (IntelliJ, NetBeans, JB) ever had problems with this workspoce and our user libraries.

Most of the time (70%), one of the projects does not build because of unresolved imports (this bug). Sometimes (10%), a user library all of a sudden is flagged "unbound classpath container". Only 20% of time a build will succeed. Needless to say that other Builders continue to build AFTER a Java Builder failed (but this is another bug of normal severity).

We got the idea that this may be related to packages appearing multiple times on the classpath (which is quite normal). We also observed that Eclipse does not notice until restart when a library changes on disk (other IDEs do -- is this normal for Eclipse or could it be part of the problem?).

Please, can somebody take care of this or announce that bugs of this kind will not receive attention? Thank You.

Eclipse Version: 3.2.1 Build id: M20060921-0945 Win XP JDK1.5.
Comment 1 Markus Schlegel CLA 2007-03-13 04:22:24 EDT
Think we have the same problem here.
Really annoying. We use UserLibraries, since our PackageExplorer Tree would simply be too large if we'd import the libraries one for one. So we've choosen to use UserLibraries (even if they are shared with every teammember).
But now, this Bug bites us every few days (I can not say what causes it, sometimes it works , sometimes not). Sometimes, a restart of eclipse helps, sometimes not. rebuilding, readding of the library does not work. 
I have to say, that our project is a large one too, but no problem with other IDE's...
Comment 2 Maxime Daniel CLA 2007-03-13 06:01:31 EDT
Please tranfer your votes to the original bug, where we'll record relevant activities towards resolution.

*** This bug has been marked as a duplicate of bug 154984 ***