| Eclipse forgets java Compiler compliance level [message #1281179] |
Mon, 31 March 2014 09:29  |
Eclipse User |
|
|
|
When initially setting up Eclipse, I set the Compiler compliance level to 1.6 in Window - Preferences - Java - Compiler.
For each project I create, I do NOT enable project specific settings in Project - Properties - Java Compiler. It shows up as 1.6.
Periodically, about twice a week, my WORKING project shows hundreds of errors. Errors that were not there before.
To correct the situation, I go into Project - Properties - Java Compiler, enable project specific settings, change the compliance level to 1.4, click apply, and click yes to the message about rebuilding the project. This, obviously, results in lots of errors.
I then change the level to 1.5, click apply, and click yes to the message about rebuilding the project. This results in significantly fewer errors.
Finally, I change the level to 1.6, apply, and rebuild. This results on NO errors, and everything is good again.
What have I missed? Why is Eclipse doing this to me?
Thank you in advance.
Steve
|
|
|
|
| Re: Eclipse forgets java Compiler compliance level [message #1281270 is a reply to message #1281205] |
Mon, 31 March 2014 12:31  |
| Eclipse User |
|
|
|
|
Is your projects output folder shared with other projects or accessed from outside of Eclipse? If something is clearing out items in this folder, it could lead to Eclipse being unable to resolve reference to classes, methods, etc. An incremental build could fail because of the unresolvable references. Is the output folder on a network drive? This could lead to issues accessing files when Eclipse is trying to resolve references.
|
|
|
Powered by
FUDForum. Page generated in 0.27083 seconds
Home