This is a test case using Play 2.0-RC1, but it is not limited to Play.

Check http://scala-ide.org/docs/tutorials/play20scalaide20/index.html for more detailed info. Those are the same steps but using eclipsify instead of sbt-eclipse.

• create a Play project
• use eclipsify to create the Scala IDE configuration
• import the project -> everything should compile
• change the signature of a template
• save all files
• refresh the application in the web browser -> compilation error
• go back in Scala IDE, refresh the workspace -> no error

Using sbt-eclipse instead of eclipsify will show an error because sbt-eclipse uses a source folder for the generated classes and eclipsify uses a class folder.

The presentation compiler is correctly informed of the source changes, but not of the class changes.

I made a attempt to fix it a while back, but it was too eager (full presentation compiler reset) 9604a17a4aa97599772b58286177b9f790af35c9. It should be done more the way it is done for the source files 795e18f5945f35f1a0220982e29e98cdffcb3fd4