You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When opening a statix signature file in Eclipse, some task seems to run that ends up writing an identical signature file to disk. This will then cause Eclipse to reload the file, which in turn triggers another analysis, which will write a file, etc.
I haven't looked to deeply into what causes this, but I suspect either moving to a hash resource stamper or preventing the writing of an indentical file would be a simple way to fix this.
This issue is slightly higher priority now that we have go-to-definition support in Statix, since that means that it becomes more likely for the user to actually open the generated files in their Eclipse instance.
The text was updated successfully, but these errors were encountered:
When opening a statix signature file in Eclipse, some task seems to run that ends up writing an identical signature file to disk. This will then cause Eclipse to reload the file, which in turn triggers another analysis, which will write a file, etc.
I haven't looked to deeply into what causes this, but I suspect either moving to a hash resource stamper or preventing the writing of an indentical file would be a simple way to fix this.
This issue is slightly higher priority now that we have go-to-definition support in Statix, since that means that it becomes more likely for the user to actually open the generated files in their Eclipse instance.
The text was updated successfully, but these errors were encountered: