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

Bug 426229

Summary: Build Automatically constantly rebuilding
Product: [Eclipse Project] JDT Reporter: Martin Spamer <Martin.Spamer>
Component: APTAssignee: Generic inbox for the JDT-APT component <jdt-apt-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: davidmichaelkarr, jarthana
Version: 4.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Sample project that includes many similar elements, but does NOT demonstrate the problem none

Description Martin Spamer CLA 2014-01-21 06:35:49 EST 
When using an Eclipse Maven Project that includes JAXB, Eclipse constantly rebuilds the project every few seconds even when no changes are occurring.

Often restarting a new build before the old build has even completed.

The root of the problem seems to be that Eclipse gets confused over the generate-sources phase reproducing source code and triggering a new build because it is later than the class files.

Possible solution: Prevent (delay) the triggering of a re-build while a rebuild is in progress therefore allowing the build to complete bring the class files more uptodate than sources in target/generated-sources.
Comment 1 Jay Arthanareeswaran CLA 2014-01-22 04:20:40 EST 
Can you extract this into a smaller project and share with us if possible?
Comment 2 David M. Karr CLA 2021-10-08 14:48:41 EDT 
Calling this FIXED is inappropriate.  Just because it's awkward to produce a project that demonstrates this doesn't mean it is not happening.  This happens to me for all of our projects that generate jaxb classes.  I could remove the source directory entry in Build Path, but then compiles fail.
Comment 3 David M. Karr CLA 2021-10-08 17:26:47 EDT 
Created attachment 287289 [details]
Sample project that includes many similar elements, but does NOT demonstrate the problem

In attempting to build a reusable test case for this problem, this is a project that includes all the elements that I would think would contribute to this, but which does NOT demonstrate the problem.  I don't know what else to do to narrow this down.  I don't know what is different about our other enterprise projects that cause this symptom to occur.