RFE: do not check while build is running
Brought to you by:
bryanth
Menu
▾
▴
Hello again,
I just noticed that CPH evaluates the Eclipse build folder while the build is still running -- which results in broken references. It requires a "Refresh" to fix that.
CPH should probably queue a job in the Eclipse scheduler, so it runs after the build.
Cheers,
Peter
PS: should I use the tracker for something like this? It seems unused and unconfigured, thus the post here.
Followup: this is actually a bigger problem since it can cause builds to fail -- Eclipse can't delete some of its output folders and thus stops building (which is of course a Windows-specific problem since other filesystems are smarter :-) ). I need to force another build sometimes to fix that problem.
Peter
Hi Peter,
Yes this has been brought to my attention before. I investigated it at one point and didn't find any documentation to explain to me how to listen for build tasks running etc.
Clearly its in Eclipse somewhere, it just didn't reveal itself to me after an hour or so of digging.
Feel free to add it as a tracker item, which I do use (I just try to fix bugs that are in there to keep the bug count at 0 :-)
Bryant
PS There is an option to have Classpath Helper monitor your build area for changes, this polling mechanism can be used to auto refresh after a build. I made this optional (with default to false), because it was slow and still didn't resolve the issues you describe in a satisfactory way.
Bryant
I think it might be sufficient to queue it up as a long-running job. My understanding is, that all jobs marked as long-running are executed sequentially, which would mean that at least the collision is avoided.
I'm not sure how you avoid running before the build. But I never used Eclipse's Job API myself, I just skimmed through some articles. Here is one:
http://www.eclipse.org/articles/Article-Concurrency/jobs-api.html
Here seems to be another:
http://www.jdg2e.com/ch29.jobs/doc/index.html
HTH,
Peter