Summary: | File changes done in an external editor not triggering rebuild (Refresh using native hooks or polling is enabled ) | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Christoph Rueger <chrisrueger> |
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | alex.blewitt, enegy, mistria |
Version: | 4.18 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Whiteboard: |
Description
Christoph Rueger
2021-01-31 14:35:01 EST
Just investigated a bit more: I found this plugin https://github.com/psxpaul/EclipseJava7Refresher which still works on Eclipse 2020-12 on MacOS 11.2.1 (Big Sur) and does exactly what I would expect. A change in an external editor takes roughly 4s until Eclipse recognizes the file change too and starts refreshing / rebuilding. The "Refresh using native hooks or polling" takes much longer... not sure exactly but > 30 seconds. I read 90s somewhere. Could "Refresh using native hooks or polling" on MacOS be changed to behave like the plugin? Also found this potentially related issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=237344 More related bugs: I think this one is pretty close to a solution: https://bugs.eclipse.org/bugs/show_bug.cgi?id=108697 and https://git.eclipse.org/r/c/platform/eclipse.platform.resources/+/74291/ @Alex: any clue here? Related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=571064 One one the main things an IDE should do, is: to start incremental builds when user clicks the SAVE button. It is tedious to wait until the Eclipse IDE finally starts a rebuild at some point..clicking SAVE should result in an incremental build without much latency..any latency longer than 10 seconds disturbs.. @Christoph: so the actual issue is not that build is not triggered, but that the change is not detected quickly enough? @Mickael I don't think so, because I can see when the build starts - it will be shown in the eclipse status bar (bottom right). I discovered when the build is started and finished: the (changed) files are immediately detected after a build was triggered. However, the latency is, that the build is not triggered immediately after I save a (java) file. The build is triggered after an undetermined duration (e.g. 10-100 seconds after saving a (java) file). A user expects that the (incremental) build is triggered immediately when its dedicated file is saved (e.g. java file) without waiting too long. (In reply to Mickael Istria from comment #5) > @Christoph: so the actual issue is not that build is not triggered, but that > the change is not detected quickly enough? Correct. |