Issues with recompilation after changing branch and refreshing projects

I've experienced this while working on a multi-module project. The steps are something like:

- open a few editors
- git checkout <another_branch_name>
- select all projects in the workspace and refresh them
- notice that the editor has some spurious compiler errors
- clean the project in question
- the errors go away

Tested with Scala IDE for Eclipse 2.0.0 beta 11 for Scala 2.9.2-SNAPSHOT.

I will try to reproduce this with an open-source project to give more precise steps, but I filed this in the meantime because Maxime said that he might be able to help with that:

https://groups.google.com/d/msg/scala-ide-user/hc1oSAisym0/mlVNT5uWVrEJ

Leave a comment

on 2011-10-05 14:37 *

By maxime.levesque

Actually my issue is different, I would describe it as

Incremental recompilation fails on project with multiple source trees

The problems might originate from the eclipse-sbt plugin that generated the project files,
I'm investigating at the moment. I'll open a new ticket for it if I don't find that there is already one.

on 2011-10-06 07:36 *

By Iulian Dragos

I think I noticed this as well. Just to understand correctly. Does the build succeed, but the presentation compiler still 'sees' the old code, and produces spurious errors?

on 2011-10-06 07:39 *

By ijuma

Exactly.

on 2011-10-06 07:46 *

By Iulian Dragos

...And the source of the errors is a dependent project, that after refresh + rebuild, should clean the errors in the main project? :)

on 2011-10-06 08:03 *

By ijuma

In at least one of the instances, cleaning the project with the errors was enough. It seems plausible that your scenario would also happen though.

on 2011-10-26 08:08 *

By Iulian Dragos

Milestone set to 2.0

on 2011-10-31 18:16 *

By Iulian Dragos

Status changed from New to Test

(In revision:d7c8779df9ac259b4fcedd1879d3210d6a9b419a) Reworked the way the presentation compiler is restarted when projects change.

- A project resets the presentation compiler of all projects that depend on it after a successful build.
- A project resets its own presentation compiler when one of the projects it depends on has changes (such as a class path change)
- A class path change, or an added source file, restarts the PC

Fixed #1000699. Test #1000645.

Branch: issue/spurious-errors-clean-build-1000699

on 2011-11-04 15:23 *

By Iulian Dragos

(In revision:c520c3766b951fc855c1ab974f1639c1477d6bcc) Reworked the way the presentation compiler is restarted when projects change.

- A project resets the presentation compiler of all projects that depend on it after a successful build.
- A project resets its own presentation compiler when one of the projects it depends on has changes (such as a class path change)
- A class path change, or an added source file, restarts the PC

Fixed #1000699. Test #1000645.

Branch: issue/spurious-errors-clean-build-1000699

on 2011-11-04 15:25 *

By Iulian Dragos