New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bad build path prevents opening files #960
Comments
Imported From: https://issues.scala-lang.org/browse/SI-960?orig=1 |
@milessabin said: |
@lexspoon said: |
@milessabin said: Presumably the new .project and .classpath files showed up as conflicting with the ones already in SVN? |
@mcdirmid said: Our only option is to make the compiler more robust with respect to classes that it expects to exist but may not exist. E.g., whoever hardcoded scala.unchecked into the compiler should make sure the compiler can live without it. |
@milessabin said: |
@odersky said: |
I just got into a state where I could not open any Scala files. I think the problem was a bad build path configuration. I don't think that a bad build path should prevent people from opening files; they should simply see type errors.
Specifically, I checked out the compiler trunk (rev 15188), and installed the current beta plugin (2.7.1.r15152-b20080522020257). I added src/compiler to my build path but not src/library. When I try to open Settings.scala, I got "class scala.unchecked not found", and then I get an editor window that has no actual editor in it. When I try to open different files, I get errors about different classes missing--scala.Predef and scala.Array come to mind. That's a scary state; it means you can't use Eclipse at all and have to break out a different editor to make any progress.
Here's one of several similar looking stack traces from my error log.
I am up and running again, but it took some perseverance. A bad build path should not prevent people from opening files; they should just get type checking errors.
The text was updated successfully, but these errors were encountered: