Community
Participate
Working Groups
State: Some projects in the workspace. Autobuild switched of. Sequence of events: I say "Build all". There is a task on some project "B": It cannot be buildt because it depends on some project "A" which does not exist in the workspace. I switch autobuild on (Window/Preferences/Perform build autom. on res. mod.). I add the missing project "A" from CVS. Result: "A" gets build, but "B" still isn't build. So I go to "B". The task is still there. Under "project", there is no option "build project", but there is an option "rebuild project". So I hit that. Finally, "B" is build. (I would have reopened bug 5109 if Bugzilla'd let me.)
Which build/drop are you running? I tried in my current 2.0.x drop and it works fine.
I'm running 2.0.1, build id 200208291828 . I just tried, I can indeed reproduce the problem, or something very much alike it. Here is what I did: Deleted project "A", including files in file space. As I have autobuild on, eclipse tries to build "B" but cannot. So it tells me "B" can no longer be built. Fine. I change my preferences to "autobuild off". I check out A from the CVS repository. Nothing gets build. I switch autobuild back on. Now, some build activity starts. When it's over, project A has been built alright. Project B, however, has a task "The project was not built since it depends on A, which failed to build." If that matters: "A" and "B" are short names I invented for this bug report. The real name of "A" sorts alphabetically later than the real name of "B". So maybe eclipse tries to built "B" first, can't do as "A" has not yet been built, and then builds "A" fine, and leaves it at that? From the messages that flash on the screen, I have a notion this is the sequence of events as they happen.
John, can you reproduce this? Is this related to http://dev.eclipse.org/bugs/show_bug.cgi?id=20689
Would the stuff they asked me to do for bug 24015 help you here, to?
This bug seems to be a specific instance of a more general problem, namely, "switching autobuild on does not always cause a complete build". That same problem has turned up in a different context, namely, in bug 24015. (Kent - to get a link to another bug in Bugzilla, just type the word "bug" followed by the bug number.) I have typed in a description of the more general problem as bug 24301. If you think that's a usefull approach, please mark this bug as a duplicate of bug 24301. If I have overlooked something or you disagree, we can continue to work on this here in this bug. (Which is why I don't resolve this as a duplicate myself.)
To answer Kent's question: > Is this related to http://dev.eclipse.org/bugs/show_bug.cgi?id=20689 I don't think so.
This works for me. I assume this was an issue with cyclic dependencies between projects? Can you confirm this works in build I20030206 (or wait until M5 is released tomorrow if you prefer).
*** Bug 24301 has been marked as a duplicate of this bug. ***
John - this was not an issue with cyclic dependencies. I don't allow cyclic dependencies between projects to crop up. I have 2.1 M4, and even with that, the problem seems to have been fixed. I cannot reproduce the bug myself any more.
Ok, Closing.
