Mysterious Scala + Eclipse Mistakes

I am writing a mixed Scala and Java program using Eclipse. Everything worked fine until about an hour ago, when it all went to hell for no apparent reason.

There is no problem in Eclipse (Scala or Java), but the Scala constructor seems to crash somewhere. It no longer creates class files. Attempting to run "Hello World" in Scala now results in a message:

Project 'projectname' contains compilation errors (therefore no binaries were created)

I use the default settings for the Scala constructor, and it worked fine before. I have not changed anything.

I tried to clean and rebuild the project several times, but to no avail. In the Build Assembly dialog box, an appearance appears that works successfully with both Scala and Java. Pure-Java parts compile and run successfully. (I temporarily commented on the places where Java calls before Scala, since the absence of Scala class files caused an import error of an unresolved class)

Is there anything in the Scala compiler error log that tells me what is going wrong? I'm going to start pulling my hair out.

I don’t remember exactly what I did, what caused it, but it would not be something exotic: write some new classes, some basic refactoring, etc.

+5
source share
1 answer

Eclipse . : -).

:

100%, AFAIR Eclipse Maven Java Scala ( , ). pom.xml , mvn compile . Maven , , JAR.

BTW Maven ~/.m2. , Unix.

+1

All Articles