Bug 144994 - rebuilding .jar does not cause compilation errors to go away
Summary: rebuilding .jar does not cause compilation errors to go away
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-06-01 18:22 EDT by Samuel B. Quiring CLA
Modified: 2009-08-30 02:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel B. Quiring CLA 2006-06-01 18:22:46 EDT
I have one project, Main, dependent on another project, Jar.  In Main I have many Java source files that depend heavily on classes that are defined in a .jar file in the Jar project.

I create a new source file in Main that depends on a class I intend to put into the .jar file.  Since it is not there yet, Eclipse shows errors in the references.  I go to the Jar project and rebuild the .jar file with the new class.  I have this .jar file checked on the Jar project's "Order and Export" list.

Once the .jar file is built, shouldn't the errors in my source go away?  Well, they are not.  I select the Jar project and hit F5.  I select the Main project and hit F5.  The errors do not go away.  I do not know how to get Eclipse to make the errors go away, except to get out of Eclipse and back in.  Very frustrating.  I've had to do it 3 times today.

The .jar file in the Jar project is created by xmlBeans.  So it changes whenever I'm doing XML schema work.  This week that is a lot.
Comment 1 Olivier Thomann CLA 2006-06-02 15:22:26 EDT
Did you refresh the project after the jar file is recreated?
Comment 2 Olivier Thomann CLA 2006-10-10 21:19:23 EDT
Closing as REMIND.
Reopen if this occurs again after a refresh.
Comment 3 Denis Roy CLA 2009-08-30 02:05:10 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.