Community
Participate
Working Groups
I20051108 When the user asks for an incremental build and a full build occurs, no feedback is provided on the reason of this full build (classpath change, external jar timestamp change, compilation participant request, etc.). We should provide this information to the user.
Martin, if JDT Core provided this information, do you think you could surface it at the UI level ?
We could imagine having a builder log similar the the console log. It would provide the reason for all previous builds since the creation of the builder log.
I think we could add more information at the running Job in the progress bar (e.g. a link similar to what CVS does). The problem there is that it goes away when the build is finished. What Oliver suggests is possible too, but I'm not so conviced yet that we should go that far. No other builder that I know has its own log. I don't really see the benefit yet.
Agreed that adding information to the progress bar is a good place. The fact that it disappears at the end is okay: the user needs this info only to explain why the build is taking more time than expected. If a full build is fast enough and the user doesn't have time to read the message, s/he won't be bothered by the fact it is a full build.
I also agree that the progress view is the best location. What form would it take ?
The progress view allows that a link. Clicking on the link could open a dialog with more detailed information.
..allows that a link is shown...
My point of having a log of build reason is that if anything wrong happens (several full builds when an incremental build is expected), we could get a trace of the order of build and their reasons. The progress bar is also a good place.
*** Bug 110407 has been marked as a duplicate of this bug. ***
