The story that the build error did not stop when using Eclipse 2020

The other day, when I was developing a Java Spring team, two team members including myself got the same error and became almost inoperable. I do not know the root cause, but from the conclusion it seems that it was a phenomenon that occurs only in the latest version of eclipse.

environment

phenomenon

If an automatic build is performed in a situation where a compile error such as a reference to an object outside the scope or a reference error of a static member occurs, the build error will be repeated as shown below. It doesn't stop until you restart Eclipse or remove Java builder from project properties → builder [^ 1]. [^ 1]: This makes the IDE just a notepad. スクリーンショット 2020-07-07 17.13.52.png

For error details 'Errors running builder'Java Builder' on project' Somehow project'. Java.lang.NullPointerException' In other words, "a nullpo occurred while the Java builder was running."

Actions tried

--Git clone again after permanently removing the project from the workspace --Change JDK version --Rebuild & reinstall dependencies

All were useless.

Solution

Dropped Eclipse version to 2019_12.

It's just this, but the build error no longer appears even though it is the exact same project. Both members are in the same situation, so I think it's probably an IDE bug. I couldn't find an article that solved a similar error, so I'll share it.

Recommended Posts

The story that the build error did not stop when using Eclipse 2020
The story that did not disappear when I tried to delete mysql on ubuntu
The story that led to solving the error because postgres did not start with docker-compose up
[Gradle] The story that the class file did not exist in the jar file
The story that Tomcat suffered from a timeout error in Eclipse
When the project is not displayed in eclipse
The story that I could not build after installing multiple Java on Windows
In WSL2, when I did `docker-compose up`, I got an error saying that the sh file was not found.
[Android Studio] About the matter that the design view is not displayed when using TextClock
The story when the container does not start up with docker-compose up and an error occurs
A story that did not work when trying to handle events in Notification Center
The story that the forced update could not be implemented
[Docker] When I did docker-compose build, I got an error saying Can not read file. .. [Rails 6.0]
A story that ended up taking a break when using the Linked List with a light feeling
The story when the test folder was not created in Rails
[Rails] The problem that pry-byebug does not stop through breakpoints
The idea of cutting off when the error is not resolved
[Docker] The story that an error occurred in docker-compose up
Error when using rails capybara
The story that the DB connection and other timeouts did not time out according to the set value
[Rails] A story that continued to incorrectly verify the reason why the update action did not pass (update)
Solved the problem that the scroll event did not fire in JQuery
The repository ... is not signed error in docker build apt-get update
What I did when the DB did not start with docker-compose up
I tried to translate the error message when executing Eclipse (Java)
How to solve the unknown error when using slf4j in Java
Unknown error in line 1 of pom.xml when using Spring Boot in Eclipse
Correspond to "error that basic authentication does not pass" in the test code "The story that could not be done"
The story of introducing Gradle as a retrofit to an existing system that did not manage packages
[Using Eclipse] Precautions when moving the workspace being created to another PC
A story I was addicted to when testing the API using MockMVC
[Java] The story that the expected array was not obtained by the String.split method.
[Rails] About the error that the image is not displayed in the production environment
The story that the Servlet could not be loaded in the Java Web application
JSESSIONID could not be assigned to the URL when using Spring Security
After verifying the Monty Hall problem with Ruby, a story that I could understand well and did not understand well