Bug 98280 - "Build Automatically" does not always work
Summary: "Build Automatically" does not always work
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-06-03 10:24 EDT by Wayne CLA
Modified: 2009-08-30 02:06 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 Wayne CLA 2005-06-03 10:24:30 EDT
The Build Automatically option does not consistently work on 3.1 M7.

For example, the Build Automatically option is on and a project may show up as 
having build errors.  Manaually cleaning the project will cause the project to 
be rebuilt and the errors to disappear.  This indicates that the Build 
Automatically option is not having an effect.

This can be very confusing for projects that were previously compiling without 
errors.  Because the project is not rebuilt, modifications made to the code 
will not have an effect.

This issue is reproducible, although there does not seem to be a consistent way 
to reproduce it.
Comment 1 Frederic Fusier CLA 2005-06-08 12:45:37 EDT
Does this problem still happen using latest RC2 nightly build or at least RC1?
Comment 2 David Mechner CLA 2005-07-03 12:51:50 EDT
I'm having a similar but not identical problem with 3.1 (I20050627-1435). I'm
using the 1.5 jdk but still have the 1.4 compatability mode on, if that matters.
 Also, I'm running on win2k, not XP. 

After making a change and doing a clean all, with "Build automatically" checked,
several of the projects will show problems (even though there are no actual
problems). Each says that it (A) can't be built until some other project B is
built. Tracing the chain of dependencies I find an erroneous problem, where A
depends on B and says B hasn't been built, but in fact B has been built without
problems. If I then clean just that project A, it (and sometimes one or two
others that depend on it) successfully build. Eventually I can get the whole
workspace built that way (I have 28 projects in the working set). 

There is another problem - not sure if it's related (but it's what's causing me
to try to rebuild all). 

We have a UnitTest program that scans through all our projects and runs all the
TestCases it finds. After making some changes, I'm often getting ClassNotFound
exception for the class I just modified when running the unit tests. After going
through the rebuilding process described above, the problem goes away and
everything runs normally. 
Comment 3 Frederic Fusier CLA 2006-08-11 05:43:16 EDT
Please reopen if this problem still occurs using 3.1.2
Comment 4 Denis Roy CLA 2009-08-30 02:06:13 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.