Error when using LogManager (l4j2) with Java 8 (java.lang.reflect.AnnotatedElement cannot be resolved)

Question

I just encountered a strange error when switching the JDK version of a new Project of mine from 7u45 to 8u20. A harmless LogManager declaration at the beginning of my class

Answer 1

Solution 1:

Try changing the source level.

1. Go to Project > Preferences > Java Compiler.
2. Enable Project specific settings
3. Set compiler compliance level to 1.4 or below.
4. Restart

Solution 2:

1. Create a new workspace.
2. Copy project files into the new workspace.
3. Import project into eclipse and rebuild.

Answer 2

When using JDK 8 and an IDE (or any other code processing tool/framework) with its own compiler, like Eclipse, you have to update the tool to a version with Java 8 support, even if you are not using the newer Java 8 features.

The reason is that the compiler must be able to load the newer class files of the JRE in order to compile your software which references these classes.

Sometimes you can get away with an older compiler when it ignores the newer version number of the class files. But some types will confuse older class file parsers as they use new features, notably AnnotatedElement, which now has default methods, and Map.Entry, an interface which now has static methods.

It seems that Eclipse does not make a difference between references for which no class file could be found and class files it failed to read when saying “«classname» cannot be resolved”.

The same applies to all tools and frameworks using ECJ as embedded compiler.

Answer 3

If this happens to you in Tomcat running from within Eclipse (question was closed as duplicate and redirects here), go to Preferences → Server → Runtime Environments → Tomcat version → Edit… and make sure the selected JRE matches the Tomcat version. (Maybe you need to install one.)

Answer 4

I was using Eclipse Helios with JRE 8 and updating the software solve the problem.

Now I'm using Eclipse Mars and works just fine -> https://eclipse.org/downloads/

Answer 5

I change from JRE 8 to JRE 7 and restart Eclipse then it works fine.