file not found manifest.mf eclipse
Asked Answered
T

12

54

I'm using the following configuration :

  • Eclipse Indigo
  • Maven 2
  • ClearCase (like SVN and CVS)

and every time I want to run an application within eclipse a popup appears telling me that a Problem has occured : File not found : ...\target\classes\META-INF\MANIFEST.MF.

Turley answered 27/4, 2012 at 11:52 Comment(3)
does the file in that path exist?Semiotics
Sorry for the late response, actually no, neither in ClearCase nor in Eclipse!Turley
#9810736Roundfaced
C
80

Go to the root of the project. Wherever the pom is located then try to do a

 mvn eclipse:clean 

Then refresh your projects and see where that leaves you

Consociate answered 28/3, 2014 at 20:36 Comment(3)
Deleting file: .project Deleting directory: .settings I guess somehow that completely destroyed it for me.Raffinate
after the clean, you should run mvn eclipse:eclipse tooNogging
mvn eclipse:clean will remove the Maven Nature for an eclipse project.Langdon
T
29

Right click on project then click on maven then do update project.It work for me.

Tumultuous answered 16/1, 2017 at 9:3 Comment(2)
This is the one that worked for me: Eclipse > Project > Maven > Update project.Uncircumcised
Thanks @Uncircumcised Eclipse > Project > Maven > Update project Works for me.Trask
B
14

I had the similar issue. What I did is:

  1. Right click on project > Maven > Disable Maven Nature
  2. Right click on project > configure> Convert to maven project

Error gone

Bugle answered 9/5, 2017 at 6:30 Comment(2)
Eclipse/maven were wrong. It's astounding this errors continue being there for years and years.Rustyrut
1/19/24 checking in. I did these steps & this solved the problemBroaden
H
8

If you're also using Maven and sometimes compiling outside of Eclipse, it could be removing Eclipse's manifest, and Eclipse won't recognize the manifest that external Maven creates.

TL;DR Uncheck "Maven Archiver generates files under the build directory" in Window > Preferences > Maven > WTP.

Read more in @cosjav's answer on another question.

Hereupon answered 11/4, 2016 at 19:26 Comment(0)
C
4

Right click on project -> Maven -> Update

DEBUG or RUN the server in order to fetch the recently created war file.

Make sure to check "Force update snapshots/releases" while doing MAVEN UPDATE

Cistaceous answered 11/12, 2017 at 12:17 Comment(0)
C
2

clean all (involved) projects and refresh your open projects in your workspace

Conchology answered 17/10, 2016 at 9:24 Comment(0)
R
2

I know this question has already been answered. After several tries, what worked for me was expanded my project in eclipse, right clicked on target directory and clicked refresh and that has been working ever since. Hope this works for someone if all the above fails.

Reorganization answered 6/2, 2018 at 13:22 Comment(1)
I followed the above , it worked for me .i have scenario like I am creating jar from one project and refering the same in another web project as dependency . Tomcat failed to start with concurrent Exception and saxparser not created error.Quadrangular
M
1

All. For me, there was an error in pom.xml. I formatted the code (Ctrl+Shift+F) and the error is gone. After that I was able to run the application.

Marmara answered 29/8, 2016 at 17:6 Comment(0)
C
0

Close the eclipse and start the eclipse again. This will refresh the projects and problem will be solved.

Confluence answered 31/10, 2014 at 15:17 Comment(1)
Not necessary to close Eclipse, just refresh the project.Contrapuntist
S
0

I had the same problem but it got resolved just disturb the formatting of

POM.xml

and press

ctrl+a and ctrl+shift+f then save the document

Sabra answered 2/11, 2017 at 4:23 Comment(0)
A
0

Right click on project then select maven and then click on Update project after select the project name and update it'll be work fine.

Apterous answered 27/2, 2019 at 5:46 Comment(1)
How your answer is different from the existing posted answer for e.g.: https://mcmap.net/q/335069/-file-not-found-manifest-mf-eclipse, if it is same, please do not post it.Outing
F
0

This issue appeared to me while I updated eclipse [updated to Eclipse 2020-12 (4.18)] as my project was open in eclipse. Then I closed my CLI (as I was running mvn test command), closed the project in eclipse and restarted my eclipse. Thereafter the issue was gone. Hopefully this will resolve your issue too.

Froehlich answered 10/1, 2021 at 11:10 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.