Eclipse에서 내 프로젝트 옆에 빨간색 느낌표가 표시되는 이유는 무엇입니까?

Eclipse에서 내 프로젝트 옆에 빨간색 느낌표가 표시되는 이유는 무엇입니까?

---

Eclipse에서 내 프로젝트 이름 위에 빨간색 느낌표가 표시 됩니다.

누구나 이것이 무엇을 의미하는지, 내가 무엇을 해야하는지 알고 있습니까?

---

이런 종류의 것을 보여주는 문제보기 (창->보기보기)가 있습니다.

JDT의 경우 일반적으로 Jars (예 : 프로젝트 구성이 존재하지 않는 jar를 참조 함)가 누락되어 있지만 JDT의 경우에는 요즘 Eclipse가 여러 가지 방법으로 사용될 수 있습니다.

---

프로젝트의 빌드 경로에 문제가 있음을 의미합니다. Android 프로젝트 인 경우 대부분 project.properties 파일에 지정된 대상 값을 찾을 수 없음을 의미합니다. 다른 종류의 빌드 문제로 인해 발생할 수도 있습니다. 그러나 주로 빌드 된 문제점에 대해서만 표시됩니다. 자세한 내용은 여기 를 참조하십시오. 그것은 일식에서 볼 수있는 내장 오류 장식에 관한 것입니다.

해당 페이지에서 추출한 내용 :

빌드 경로 문제는 때때로 프로젝트의 다른 문제 중에서 놓치기 쉽습니다. 패키지 탐색기 및 프로젝트 탐색기보기에 빌드 경로 오류가 포함 된 Java 프로젝트 및 작업 세트에 대한 새 데코레이터가 표시됩니다.

구체적인 오류는 문제점보기에서 볼 수 있으며보기 메뉴를 열고 그룹화> Java 문제점 유형을 선택하면 모두 빌드 경로 카테고리에 표시됩니다.

---

또한이 문제가 여러 번 발생했으며 "문제점"탭에서 메시지를 삭제하고 프로젝트를 다시 빌드하여 문제를 해결할 수있었습니다. 프로젝트를 선택하고 메뉴 막대를 클릭 Project -> Clean...하여 프로젝트를 다시 선택한 다음 확인하십시오.

---

빌드 경로에 이미 삭제 된 jar 파일이있을 수 있습니다. 프로젝트를 마우스 오른쪽 버튼으로 클릭하십시오. 속성-> Java 빌드 경로 및 거기에서 삭제 된 jar 파일을 제거했습니다.

---

몇 가지 이유가있을 수 있습니다. 대부분의 경우 다음 이유 중 일부일 수 있습니다.

1. / lib 폴더에서 일부 .jar 파일을 삭제했습니다.
2. 새로운 .jar 파일을 추가했습니다
3. 다른 사람과 충돌 할 수있는 새 .jar 파일을 추가했습니다

따라서해야 할 일은 누락 / 업데이트 / 새로 추가 된 jar 파일을 해결해야합니다.

1. 프로젝트를 마우스 오른쪽 버튼으로 클릭하고 go to properties
2. 고르다 Java Build Path
3. Libraries탭으로 이동
4. 이미 제거한 jar 파일의 참조를 제거하십시오. 근처에 빨간색 표시가있어 쉽게 식별 할 수 있습니다.
5. 다음을 사용하여 새로 추가 된 .jar 파일에 대한 참조를 추가하십시오. Add JARs
6. 프로젝트 새로 고침

위의 이유 중 하나로 인해 문제가 해결됩니다.

---

프로젝트-> 마우스 오른쪽 버튼으로 클릭-> 속성-> Java 빌드 경로-> 라이브러리로 이동하십시오.

아이콘에 적십자 기호가있는 모든 JAR을 삭제하십시오.

해결되었습니다.

---

이것은 아마도 빌드 문제 일 것입니다. 마이 븐으로 프로젝트를 업데이트 한 고정 문제 (Alt + F5)

---

Eclipse 도구에서 순환 종속성을 "경고"로 표시하면 "빌드 경로에서 사이클이 감지되었습니다"오류가 발생하지 않습니다. 이클립스에서 :-> Windows-> 환경 설정-> Java-> 컴파일러-> Buliding-> Circular Depencies

감사

---

솔 루틴 1 :

1 단계

Right click on your project -> Close Project. it will Close your project and all opened file(s) of the project

step:2

Right click on your project -> Open Project. it will Open your project and rebuild your project, Hope fully it will fix red exclamation mark

Solution 2:

Step:1

Right click on your Project -> Properties -> Java Build Path. Can you see missing in front of your library file(s) as per following screen-shot

Step:2 Click on Add Jar to select your Jar file if it is the placed in WEB-INF/lib of your project or Add External Jar if jar file placed somewhere on your computer

Step:3 Select the old missing file(s) and click on Remove click here for image

Solutioin 3: Right click on your Project -> Properties -> Java Build Path -> JRE System Library and reconfigure the JRE

and go to your project and remove .properties and .classpath in your project directories.

backup your project data and create a new one and follow the solutions 1 & 2

---

This is common, you will need to do the following steps:

1- Right click on the project

2- Build path

3- Configure Build Path

4- Remove jars/projects that had moved from their old path

5- clean the project

6- build the project "if not automatically built"

7- Add the jars/projects using their new locations

Run and that is it!

---

Isn´t it a strange behavior? In my case, the mistake was that I added a jar-lib. But this lib was faulty, so I removed the lib. But, no matter what I´ve done, the error still exists. I removed the jar-file, even with the eclipse option "remove from build-path", deleted it on my project-folders and cleaned my project, but nothing worked. Only after I´ve done the way Qwert has described, it worked. But sould an IDE not independent from error messages? The error was fixed, only the messages caused the problem. Thanks to Qwert (if I got enough reputations, I will vote your answer. But now I am not able to, sorry).

---

I had a maven project giving me same thing. It showed that it couldnt find the jar with that version (dependency) and I knew its there and is correct -

So, for me the solution was to 1 delete the local repository. 2 Clean the project. 3 Disable the maven nature. 4 Generate eclipse artifacts and 5 re-configure as maven project.

(in order)

---

My problem concerning exclamation mark was in the section: "right click on project folder" - Properties - Libraries tab. There was an Error marked in red on a libray that probably wasn't in the right place so I removed it and ex. mark disappeared. The problem raised after deleting some old projects.

---

If your IDE doesn't find JRE from the path you given. Then you manually need to add JRE path in eclipse to remove red exclamation mark from the project. To do this please follow below steps :-

Go to to Properties>Java Build Path>Libraries> Click on Edit

Then Select Alternate JRE and click on Finish.

Note : If you don't have Java Run time Environment (JRE) installed, please install.

---

i was having the same problem....the actual issue was missing .jar file which took palce coz of changing my workspace. i just deleted the appcompat folder(which has the".jar" file) from my new workspace and copied it from my old workspace. this solved my problem.

---

This is may for one reason, If a project contains library project then you need to clean first the library project have been used, then clean the project contains that library project.

---

Mainly this problem occurs because your library files get deleted. The simple way to work your project as it was working previously is 1) Go to Project properties 2) Select java Build Path 3) Remove all library except jre. 4) Now add the same same jar file by clicking "Add external jars".

---

use this simple steps right click on the project->properties ->java Build path-> click on the jre system library and remove it after that step click on Add library and add a new jre system library that will resolve it!

---

For Maven project delete the project from IDE and run the maven command :-mvn eclipse:clean ,mvn eclipse:eclipse,mvn clean install -e .After this import the project on IDE. This stuff is works for me.

---

If you are facing same issue :

1. Recall , if you have changed the place where you used to keep the jars and add it in build path .
2. If you have moved your project from one machine to another then you need to right click on project-> Build Path -> Configure Build Path . In Tab Order and export you would see the place where eclipse is searching for jars , just keep it there and refresh the project.
   3. If above things don't work , try Project -> clean .

---

This is related to multiple versions of same depenendency in the local repository .m2

go to ur eclipse > problems tab > see the errors > go the local .m2 folder

delete all the non relevant versions of the the dependency which you have added recently.

then try to rebuild the project.

---

I too faced this strange situation. What I got to know is that, earlier I ran my spring projects with Spring version 1.5.4 and later for one project I chose version 2.0.1. That's when I got this error. When I visited POM and changed Spring version to 1.5.4 manually, the error was gone. What I guess is that, maven downloads the required JARs according to the Spring version specified. If you change the version, maven won't download JARs if those JARs are already downloaded for previous Spring version and found in .m2 source folder found as C: -> Users -> "Logged-In-User-Name" -> .m2 path.

What I did again was to keep the Spring version as it is (as 2.0.1), I opened the Problems view as said earlier and I deleted the JARs which were said as not found in the Problems view by visiting .m2 folder (the Paths were mentioned in the Problems view for were the JARs are). I then updated the maven and all problems were gone.

That's how I conclude that the problem was with JARs which were downloaded for the previous Spring versions in .m2 folder.

---

I Solved this problem by:

step 1: C:/user/rafiq/.m2/repository --> Delete this folder

Step 2: right click on your project-->maven-->update maven project-->check only clean project-->ok.

Step 3: right click on your project-->maven-->update maven project-->check only update project-->ok.

Problem Solved.

---

If you change the location of the jars from selenium-java-3.13.0 folder this mak will appear. So restore the original location of the jars and you are go to go.

---

It means the jar files are missing from the path that you have given while configuring Build Path/adding jars to the project.

Just once again configure the jars.

---

In my case this is incorrect/improper dependency

Markers > Problems is highlighting spring/.gradle/cache/httpcomponents.......pom is not valid archive

I removed

compile group: 'org.apache.httpcomponents', name: 'httpcomponents-client', version: '4.5.6', ext: 'pom'

changed to

compile group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.5.6'

---

To Remove RED EXCLAMATION mark on project,
I have deleted all JAR files using BUILD Path--> LIBRARY --> ADD EXTERNAL JARs and remove all or selected JAR.
Reinstall again.
This action resolve my issue with Red exclamation mark.

---

What worked for me (and probably not yet answered here till now) ::

Selenium 프로젝트와 ANT에서 작업하는 동안 프로젝트의 ROOT 디렉토리에있는 두 가지 소스에서 서로 다른 "BUILD.xml"파일을 복사하여 두었습니다. 이 RED-EXCLAMATION-MARK가 발생하여 BUILD.xml 파일 중 하나를 다른 폴더로 이동하자마자 사라졌습니다.

"하나의 프로젝트에 두 개의 BUILD.xml 파일이있는 이유는 무엇입니까?"에 대해서는 실제로 다양한 BUILD.xml 파일에서 ANT의 구성을 가지고 놀고있었습니다.

참고 URL : https://stackoverflow.com/questions/6040914/what-is-the-reason-for-a-red-exclamation-mark-next-to-my-project-in-eclipse