Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 158779 - Eclipse reports that required library's are missing when in fact they aren't.
Summary: Eclipse reports that required library's are missing when in fact they aren't.
Status: CLOSED DUPLICATE of bug 161631
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 1.0.1   Edit
Hardware: PC Windows XP
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: jst.j2ee CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-26 11:17 EDT by Mike Franek CLA
Modified: 2007-04-03 11:46 EDT (History)
1 user (show)

See Also:


Attachments
Picture of the problem in action! (316.48 KB, image/png)
2006-09-26 11:30 EDT, Mike Franek CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Franek CLA 2006-09-26 11:17:14 EDT
We have a very large code base that includes 19 individual projects.  One of these products contains all of the required libraries for both compilation and runtime.  This project that contains the libraries is a tomcat projct.  The structure of the libraries is:

B2BGateway 
     webapp
         WEB-INF
            lib
               << all the various jar files go here >>

whenever the project is updated to either replace some / all of the above jars, the other projects now show errors that the specific required library is missing and compilation halts.

The ONLY remedy (refreshing the projects does not work) is to remove the jar from the classpath, close the window, and re-add the same jar you just deleted.  You do not have to do ANYTHING between the delete and the add.  With 19 projects and roughly 30 jars, this is obviously a nightmare.  I have also found that by simply modifying the .classpath file (adding a blank line and then removing it) and then saving the file, the compilation error will go away.  This tells me there is something in the "history" that might possibly be corrupt.  I am not the only one to experience this behavior as others on my team also experience the same issue.  This is currently in 3.2 and I have also seen it in 3.1.
Comment 1 Mike Franek CLA 2006-09-26 11:30:03 EDT
Created attachment 50909 [details]
Picture of the problem in action!

Here is a graphic showing the problem in action!
Comment 2 Philipe Mulet CLA 2006-10-16 04:58:47 EDT
Could you pls provide steps to reproduce ? Pls reopen then.
Comment 3 Mike Franek CLA 2006-10-23 15:08:46 EDT
Great, just close the ticket without even an email asking for assistance of any kind.  Really shows me how much you wish to address an obvious problem.  I tried..
Comment 4 Olivier Thomann CLA 2006-10-23 15:57:26 EDT
comment 2 is a request for assistance.
We need steps to reproduce the failures in order to investigate it. Simply reopen if you have steps to reproduce. If you can only get it inside a big workspace and you can provide the workspace (no problem with proprietary code), then we will find a way to make the transfert.
Comment 5 Christian Holm CLA 2006-12-15 03:55:21 EST
I have been seeing the same problem in our team. Sometimes you can get the projects to start compiling again by refreshing all projects, but other times even refresh and clean of all projects will not make Eclipse discover the library.

Our setup is similar to the original submitters, with a "commons"-project, which outputs jar-files, which are referenced by the other projects.

I have not yet found any precise way to reproduce the problem, it just seems to occur at random times. I suspect that one possibility is that an updated jar is discovered during the ant build process, when the jar is not yet complete, but this have been hard to reproduce.
Comment 6 Frederic Fusier CLA 2006-12-15 09:42:40 EST
Mike, Christian,
Looking at your library folder hierarchy that your project is a Web project... Could you confirm this assumption?
Comment 7 Christian Holm CLA 2006-12-18 04:44:37 EST
Actually we have a full J2EE stack divided into several projects (base/utility, hardware plugins, export/import plugins, EJB, webstart client, web client and so on). I will check with our lead developer if I can send you the entire workspace. It is however proprietary and quite big (around 500 mb), so I don't know if that is the easiest way to go.

I will try to be more vigilant the coming days, and see if I can pinpoint exactly when and why it occurs. Is there any debug log-option I can turn on, so I can send you the log-files and the timestamps of when the problem occured?
Comment 8 Christian Holm CLA 2006-12-18 09:42:08 EST
I just had the following occur:

* Added a public static final field to a class in our parent base-project.
* Recompiled and jar'ed the project using ANT.
* Refreshed the base-project.
* Tried to use the new field in the child EJB-project, but the editor reported a compilation error. Content-assist could not pick up the new field either.
* Control-clicked on the class to get the .class file displayed, and found that it contained the new field.
* Saw that the class where I tried to use the new field was not marked as having compile errors in the package explorer.

I realise this is not the exact same problem as the one reported originally in this bug, but it seems to me that it could come from the same problem.
Comment 9 Mike Franek CLA 2006-12-18 15:47:28 EST
Based on additional users with the same issue, I'm going to re-open.  As I have stated before, there is no step 1....4 to re-create.  It just kind of shows up from time to time.
Comment 10 Mike Franek CLA 2006-12-18 15:49:09 EST
yes, ours is basically a webapp.  The jars that go into the lib folder of the webapp are build within the workspace via ant.  Please look at the picture of the problem in action for the complete project layout as it pertains to my interest.
Comment 11 Frederic Fusier CLA 2006-12-19 03:41:28 EST
Mike, Christian,

Looking at your description, it sounds like your problem is similar than this described in bug 161631 => I move your bug to Web Tools component to set it as duplicate...

Thanks for the feedback
Comment 12 Frederic Fusier CLA 2006-12-19 03:41:53 EST

*** This bug has been marked as a duplicate of bug 161631 ***
Comment 13 John Lanuti CLA 2007-04-03 11:46:35 EDT
Closing as part of mass query to clean up old resolved bugs in untargetted milestones.