Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Eclipse faceted project metadata file could not be read

Tags:

eclipse

Every now and then, I get this error in one of my Eclipse projects:

Faceted project metadata file "/project/.settings/org.eclipse.wst.common.project.facet.core.xml" could not be read.

This is a team project using Git. The ".settings" directory does not exist at all.

I'm not sure what project "facets" in Eclipse really are. Does anyone know what this error means or how to fix it?

like image 642
David Avatar asked May 07 '14 12:05

David


People also ask

Why could not open resource metadata file?

Could not open resource metadata file - no such file, what can i do? how could i fix the error? Your resource is too old and has not been updated to work with newer artifacts. Update your resource by converting __resource.lua into fxmanifest.lua.

How do I set project facets in Eclipse?

The project facets should be derived automagically by the M2Eclipse plugin from the POM configuration. If you make some changes to the POM and need Eclipse to take them into account, right-click on your project, then go to Maven > Update Project Configuration. You should not set project facets manually.

Where are the required meta-data for Maven-Eclipse-plugin?

All the required meta-data are in the POM: JDK level version, Servlet API, etc. Developers don't have to set this manually after an import or any other POM update, which is a good thing. This applies also to the maven-eclipse-plugin (that generates the facet based on the POM meta-data).

How to match the Java compiler and project facet version?

1- Manually make sure the two versions match. - Select the right compiler level in the provided dialog and click 'Finish'. Taken from Eclipse: Java compiler level and project facet mismatch Also gives location of where you can access the Java compiler and facet version.


3 Answers

Right click the project in eclipse and go to Project Facets and change the java or the corresponding Project Facets to the version that it was developed.

Right click the project folder --> Properties --> Project Facets --> Change java version or tick the required module choosing the version.

like image 134
Uva Avatar answered Oct 24 '22 09:10

Uva


I resolved it this time by re-importing the Maven project. This recreated the .settings directory and eliminated the error.

like image 34
David Avatar answered Oct 24 '22 08:10

David


I resolved it this time with Right click --> Project --> Properties --> Target Runtimes --> tick the required runtime. In my case no runtime was selected.

like image 6
Diddi Avatar answered Oct 24 '22 10:10

Diddi