Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 183739

Summary: [buildpath] Build path problem is not removed
Product: [Eclipse Project] JDT Reporter: Eiji Morito <eiji.morito>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: don, hinaba
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug
Attachments:
Description Flags
Reproduceable projects none

Description Eiji Morito CLA 2007-04-24 04:22:45 EDT 
Build ID: I20070323-1616

Steps To Reproduce:
1. Create a java project A, which create jar file on build. This can be done by adding ant builder on builder.
2. Create another java project B, which references jar file created on project A. To do this, just add jar created by project A to the build path of project B.
3. Delete both project A and B from workspace, but don't delete contents of the projects.
4. Delete jar file created in project A.
5. Import project B.
6. Import project A.
7. The Build path problem that says "Project 'B' is missing required library." does not remove from Problem view. This build problem does not remove even if clean or build all is invoked.

More information:
Comment 1 Eiji Morito CLA 2007-04-24 04:34:01 EDT 
Created attachment 64692 [details]
Reproduceable projects

I attached projects to reproduce.
If project MyCalendar is imported first, and java1 next, no error is diaplayed on Problem view.
If project java1 is imported first, and MyCalendar next, the build path problem is displayed on Problem view. This problem will not be removed by
Build all, or clean.
Comment 2 Jerome Lanneluc CLA 2007-06-21 04:47:27 EDT 
To be investigated for 3.4.

See also bug 58649.
Comment 3 Donald Gordon CLA 2007-08-28 18:31:46 EDT 
I have what I think is exactly the same problem when projects refer to JARs in their classpath that are on the network.

If the network is down, Eclipse seems to decide that those JARs are inaccessible and flags them as build path errors (which is ok).

But even if they are again made accessible and a clean or build all is initiated, the build path errors persist.  The only way to make those projects build again is to edit the build path entries to point to some other path (which need not exist), save the build path settings, then edit the build path entries to point back to their original locations and save the build path settings again.

A similar issue occurs when the build path entries use variables to define the path: if the variable contents change then the build path entries will still be in error -- this is a real pain when checking projects out of SVN.
Comment 4 Jerome Lanneluc CLA 2007-08-29 04:00:21 EDT 
Donald, it sounds like you are seeing a slightly different problem than the one reported here. This bug is about a builder that adds a jar file before the Java builder runs and the Java builder doesn't see that the classpath has been fixed. What you are seeing is most likely bug 201062. You might want to annotate bug 201062 instead.
Comment 5 Jerome Lanneluc CLA 2008-05-12 05:14:47 EDT 
We ran out of time to fix this for 3.4. Deferring.
Comment 6 Eclipse Genie CLA 2020-02-21 14:01:19 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.