Community
Participate
Working Groups
If you attempt to open an Maven project/Eclipse workspace that has been converted to use JDK 11 in an Eclipse IDE that doesn't support JDK 11 Eclipse the following will happen: * The workspace log fills up with error messages like: "Could not determine language level, using default 1.5" and "Could not determine source level, using default 1.5" * Eclipse will automatically *without any prompt to the user* change the project settings for all projects in the workspace. The Java Compiler will now have "Enable project specific settings" checked and "Use compliance compliance from execution environment 'J2SE 1.5'. At this point, on a large project, there will be hundreds of compiler errors. The entire IDE will slow down and become completely unusable. **There is no easy way to fix this.** A user must either right-click on each individual project and unselect 'Enable project specific settings' (which takes ages on a large workspace with dozens of modules) or she must create a whole new workspace. **This is extremely malicious behavior.** Eclipse should never 'Enable project specific settings' without the user's explicit permission. Eclipse should never change the language level for a project without the user's explicit permission. I can't think of any condition where this behavior would actually be desired by the developer. Any other behavior that does not corrupt an entire workspace is strongly preferred.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
