Im getting the following error in eclipse:

The persistence.xml file does not have recognized content.

My persistence.xml file works great in my application but eclipse keeps giving me this error.  I got this after moving the file and updating my project configuration with m2eclipse. I did not change the file itself. Anyone knows how to solve this?

persistence.xml:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
    &lt;persistence version=&quot;2.0&quot; xmlns=&quot;http://java.sun.com/xml/ns/persistence&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=&quot;http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd&quot;&gt;
    	&lt;persistence-unit name=&quot;localDB&quot; transaction-type=&quot;RESOURCE_LOCAL&quot;&gt;
    		
    		&lt;provider&gt;org.apache.openjpa.persistence.PersistenceProviderImpl&lt;/provider&gt;
    		&lt;class&gt;package.Users&lt;/class&gt;
    		&lt;properties&gt;
    			&lt;!-- enable warnings for debugging --&gt;
    			&lt;property name=&quot;openjpa.Log&quot; value=&quot;DefaultLevel=TRACE, Runtime=INFO, Tool=INFO, SQL=TRACE&quot;/&gt;
    			&lt;!-- connection properties --&gt;
                &lt;property name=&quot;openjpa.ConnectionURL&quot; value=&quot;jdbc:mysql://localhost/test&quot;/&gt;
                &lt;property name=&quot;openjpa.ConnectionDriverName&quot; value=&quot;com.mysql.jdbc.Driver&quot;/&gt;
                &lt;property name=&quot;openjpa.ConnectionUserName&quot; value=&quot;root&quot;/&gt;
                &lt;property name=&quot;openjpa.ConnectionPassword&quot; value=&quot;&quot;/&gt;
                
    		&lt;/properties&gt;
    	&lt;/persistence-unit&gt;
    &lt;/persistence&gt;

**Update**

Looks like a bug in m2eclipse in combination with jpa.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=251323

Temporarily solved by setting the option to show it as a warning instead of an error 

Eclipse does not recognize content of persistence.xml

Ugh!  My Eclipse is stuck in an endless loop:

 - No operations to display at this time
 - Refreshing Workspace Building
 - Workspace. Invoking &#39;Maven Project Builder&#39; on /MobileWebApp

The building workspace never gets past 58%.

Details:

Google&#39;s GWT provides a sample app MobileWebApp.  They [suggest adding it to Eclipse][1] via File &gt; Import &gt; Checkout Maven projects from SCM.

I followed the instructions in [this blog][2] for adding the plugins for m2e, subclipse, and the m2e-subclipse connector.

After installing the plugins, I imported the sample project via File &gt; Import &gt; Checkout Maven projects from SCM and [this URL][3].

The import seemed to complete ok and Eclipse doesn&#39;t display any markers.  But now I have this endless refreshing and building and have no clue what is causing it or how to fix it.

Versions:

 - Eclipse Indigo 3.7
 - m2e 1.0.100 
 - m2e connector for build-helper-maven-plugin 0.14 
 - Maven SCM handler for Subclipse 0.13
 - Subclipse 1.6.18
 - Subclipse Client Adapter 1.6.12

Any advice is greatly appreciated.


  [1]: http://googlewebtoolkit.blogspot.com/2011/09/working-with-maven-and-requestfactory.html
  [2]: http://www.shareyourwork.org/roller/ralphsjavablog/entry/eclipse_indigo_maven_and_svn
  [3]: http://google-web-toolkit.googlecode.com/svn/trunk/samples/mobilewebapp

Eclipse loops endlessly: Invoking &#39;Maven Project Builder&#39;

i was wondering if it&#39;s possible to configure run as maven install in eclipse to skip unit tests, if such thing is doable, then please tell me how to do it, thanks in advance.

How to configure maven install to skip tests in eclipse?

I&#39;m not very experienced with Maven in combination with Android yet, so I followed [these][1] instructions to make a new Android project. When the project has been created, I get the following error message: 

&gt; Project &#39;xxx-1.0-SNAPSHOT&#39; is missing required source folder:
&gt; &#39;src/test/java&#39;

When I try to add a new source folder with New-&gt;Other-&gt;Java-Source Folder with src/test/java, I get another error message:

&gt;  The folder is already a source folder.

But I don&#39;t have any src/test/java folder in my project. How should I deal with that? What&#39;s the clean way to setup the project, because I assume that there is something missing in this instruction. So what is the Maven way to let src/test/java appear?

I&#39;m using Eclipse Juno, m2e 1.1.0, Android Configuration for m2e 0.4.2.

  [1]: http://rgladwell.github.com/m2e-android/

How to deal with missing src/test/java source folder in Android/Maven project?

I&#39;m trying to build a `Dynamic Web Application` in eclipse using Java 8 (and Wildfly appServer if that matters) but I&#39;m unable to make Eclipse Luna M5 use Java 8 (I do have Java 8 BETA support installed and it works on JavaSE projects). 

In my POM I set the level to Java 8:

    &lt;plugin&gt;
        &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
        &lt;version&gt;3.1&lt;/version&gt;
    	&lt;configuration&gt;
    		&lt;source&gt;1.8&lt;/source&gt;
    		&lt;target&gt;1.8&lt;/target&gt;
    	&lt;/configuration&gt;
    &lt;/plugin&gt;

But after I do `maven -&gt; update project` I get the following error:

    Could not update project ExampleApp configuration
    Version 1.8 of project facet java does not exist.

And indeed there is no java 1.8 project facet under `project-&gt;preferences-&gt;project facets-&gt;java`

Can I manually create such `facet` and add It to to eclipse or I&#39;ll have to wait until java 8 is released and the eclipse guys decide to add it ?



Version 1.8 of project facet java does not exist

I am trying to work with [Spring Data and Neo4j][1]. I started by trying to follow [this guide][2] linked to by the main site. In particular I based my pom.xml off of the [&quot;Hello, World!&quot; example file][3]. Here is a snip from my pom.xml for the plugin that is causing the issues...

&lt;!-- language: xml --&gt;

    &lt;plugin&gt;
    &lt;!-- Required to resolve aspectj-enhanced class features --&gt;
        &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
        &lt;artifactId&gt;aspectj-maven-plugin&lt;/artifactId&gt;
        &lt;version&gt;1.0&lt;/version&gt;
        &lt;configuration&gt;
            &lt;outxml&gt;true&lt;/outxml&gt;
            &lt;aspectLibraries&gt;
                &lt;aspectLibrary&gt;
                    &lt;groupId&gt;org.springframework&lt;/groupId&gt;
                    &lt;artifactId&gt;spring-aspects&lt;/artifactId&gt;
                &lt;/aspectLibrary&gt;
                &lt;aspectLibrary&gt;
                    &lt;groupId&gt;org.springframework.data&lt;/groupId&gt;
                    &lt;artifactId&gt;spring-data-neo4j&lt;/artifactId&gt;
                &lt;/aspectLibrary&gt;
            &lt;/aspectLibraries&gt;
            &lt;source&gt;1.6&lt;/source&gt;
            &lt;target&gt;1.6&lt;/target&gt;
        &lt;/configuration&gt;
        &lt;executions&gt;
            &lt;!-- ERROR HERE IN ECLIPSE SEE BELOW FOR FULL MESSAGE --&gt;
            &lt;execution&gt;
                &lt;goals&gt;
                    &lt;goal&gt;compile&lt;/goal&gt;
                    &lt;goal&gt;test-compile&lt;/goal&gt;
                &lt;/goals&gt;
            &lt;/execution&gt;
        &lt;/executions&gt;
        &lt;dependencies&gt;
            &lt;dependency&gt;
                &lt;groupId&gt;org.aspectj&lt;/groupId&gt;
                &lt;artifactId&gt;aspectjrt&lt;/artifactId&gt;
                &lt;version&gt;${aspectj.version}&lt;/version&gt;
            &lt;/dependency&gt;
            &lt;dependency&gt;
                &lt;groupId&gt;org.aspectj&lt;/groupId&gt;
                &lt;artifactId&gt;aspectjtools&lt;/artifactId&gt;
                &lt;version&gt;${aspectj.version}&lt;/version&gt;
            &lt;/dependency&gt;
        &lt;/dependencies&gt;
    &lt;/plugin&gt;

The error I am seeing is:

     Multiple annotations found at this line:
        - Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.0:compile (execution: default, phase: process-classes)
        - Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:aspectj-maven-plugin:1.0:test-compile (execution: default, phase: process-classes)

I am running Eclipse 3.6.2 and m2e 0.13. I&#39;m not a Maven expert, so please be very explanatory in your answers if possible.

I&#39;ve also tried [m2e 1.0.0][4] via [this update site][5] and still get the same error.

  [1]: http://www.springsource.org/spring-data/neo4j
  [2]: https://github.com/SpringSource/spring-data-graph
  [3]: https://github.com/SpringSource/spring-data-graph-examples/blob/master/hello-worlds/pom.xml
  [4]: http://www.eclipse.org/m2e/download/
  [5]: http://download.eclipse.org/technology/m2e/milestones/1.0


How to solve &quot;Plugin execution not covered by lifecycle configuration&quot; for Spring Data Maven Builds

I have created a New Dynamic Project under Eclipse Helios Version, where my JRE Version is set to 1.6.
I have added Maven capabilities to the Web Application by clicking on _Configure_ → _Convert to Maven Project_.

After adding this, a build error appeared in the Eclipse Problems view:

    Java compiler level does not match the version of the installed Java project facet.
    Unknown	Faceted Project Problem (Java Version Mismatch)



Please tell me how to resolve this error (I want to have my JRE version as 1.6 only).




Java compiler level does not match the version of the installed Java project facet

I imported a Maven project and it used Java 1.5 even though I have 1.6 configured as my Eclipse default `Preferences-&gt;Java-&gt;Installed JREs`. 

When I changed the Maven project to use the 1.6 JRE it still had the build errors left over from when the project was using Java 1.5 (I described these build errors earlier in: https://stackoverflow.com/questions/3538524/i-have-build-errors-with-m2eclipse-but-not-with-maven2-on-the-command-line-is-m)

I&#39;m going to delete the project and try again but I want to make sure this time that it uses Java 1.6 from the start to see if this eliminates the build problems.

How do I make sure the project uses Java 1.6 when I import it?

What causes imported Maven project in Eclipse to use Java 1.5 instead of Java 1.6 by default and how can I ensure it doesn&#39;t?

I&#39;m a beginner at Maven and I&#39;ve played with it from a command line point of view a little, so now I was trying to use it in Eclipse; I installed the m2eclipse plugin to do so.

But I&#39;m stumped from the very beginning! Apparently I&#39;ve missed a bit of terminology somewhere along the line. I can&#39;t keep track of all these new Maven terms... **What is a Maven Project, and what is a Maven Module?** These are my options when creating a new project in the Maven category in Eclipse.

Maven &quot;Module&quot; vs &quot;Project&quot; (Eclipse, m2eclipse plugin)

    org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.5
        at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:129)
        at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:48)
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:142)
        at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:261)
        at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:185)
        at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:152)
        at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:386)
        at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:865)
        at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:355)
        at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:66)
        at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:87)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:414)
        at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:351)
        at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:74)
        at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
    Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.5
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:296)
        at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:186)
        at org.sonatype.aether.impl.internal.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:279)
        at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:115)

I have read where many people were able to solve this by:

- Deleting the folder from the local repository and letting it re-download it (this did **not** work)

- By configuring eclipse to target your maven installation instead of the embedded one as described here (this did **not** work)

  https://stackoverflow.com/questions/7378279/could-not-calculate-build-plan-artifact-org-apache-maven-pluginsmaven-resource

**I am new to Maven** so please excuse any of my ignorance.

This project is working on another machine, and just pulled it down from the repository on this one, with the same version of eclipse and m2e plugin installed. I have been fooling with this for over 10 hours now and it is driving me nuts (Maven has been nothing but headaches for me so far...)

### EDITS

After looking closer I did notice that it is not downloading the .jar files into the local repository... I am not sure if that is something obvious...

I am not given the option to add Maven Dependencies to the build path.

Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved

It&#39;s my first couple of days learning Maven and I&#39;m still struggling with the basics. I have an external .jar file (not available in the public repos) that I need to reference in my project and I&#39;m trying to figure out what my best option is. 

It&#39;s a small scale project without a central repository for libraries, so it has to be either a local repository (somehow added to source control, don&#39;t know if it&#39;s supposed to work that way?) or the .jar needs to be stored on disk outside of any formal repository.

1) What&#39;s my best option for adding the .jar file to my project&#39;s references with maven given that I want both the project and the library to be in source control?

2) I still can&#39;t seem to have Eclipse see the dependency. I manually added it to the &lt;dependency/&gt; section of the pom, and it shows up fine in the Dependencies list in m2eclipse. mvn compile and mvn package both succeed, but running the program results in:

    Exception in thread &quot;main&quot; java.lang.Error: Unresolved compilation problems:
            LibraryStuff cannot be resolved to a type

This is after editing the POM as:

    &lt;dependency&gt;
      &lt;groupId&gt;stuff&lt;/groupId&gt;
      &lt;artifactId&gt;library&lt;/artifactId&gt;
      &lt;version&gt;1.0&lt;/version&gt;
      &lt;systemPath&gt;${lib.location}/MyLibrary.jar&lt;/systemPath&gt;
      &lt;scope&gt;system&lt;/scope&gt;
    &lt;/dependency&gt;

Should I be executing mvn install:install-file even thought I already have the pom.xml edited as above?

Thanks!

Maven: best way of linking custom external JAR to my project?

I&#39;m compiling a project in Eclipse using m2eclipse. I set the JDK path in Eclipse like this:

    Windows--&gt;preferences--&gt;installed jres--&gt; jdk1.7.xx  path

But this is showing an error

    [ERROR] COMPILATION ERROR :
    [INFO] -------------------------------------------------------------
    [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE    rather than a JDK?
    [INFO] 1 error
    [INFO] -------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 1.424s
    [INFO] Finished at: Tue Oct 29 15:21:01 IST 2013
    [INFO] Final Memory: 5M/15M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-   plugin:3.1:compile (default-compile) on project TEST-WEB: Compilation failure
    [ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?


No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

I have a fairly simple Maven project:

&lt;!-- language: xml --&gt;

    &lt;project&gt;
        &lt;dependencies&gt;
            ...
        &lt;/dependencies&gt;
    
        &lt;build&gt;
            &lt;plugins&gt;
                &lt;plugin&gt;
                    &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
                    &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
                    &lt;version&gt;2.4&lt;/version&gt;
                    &lt;executions&gt;
                        &lt;execution&gt;
                            &lt;id&gt;copy-dependencies&lt;/id&gt;
                            &lt;phase&gt;package&lt;/phase&gt;
                            &lt;goals&gt;
                                &lt;goal&gt;copy-dependencies&lt;/goal&gt;
                            &lt;/goals&gt;
                            &lt;configuration&gt;
                                &lt;outputDirectory&gt;${project.build.directory}/dependencies&lt;/outputDirectory&gt;
                            &lt;/configuration&gt;    
                        &lt;/execution&gt;
                    &lt;/executions&gt;
                &lt;/plugin&gt;
            &lt;/plugins&gt;
        &lt;/build&gt;
    &lt;/project&gt;

However, I get the following error in m2eclipse:

    Description	Resource	Path	Location	Type
    maven-dependency-plugin (goals &quot;copy-dependencies&quot;, &quot;unpack&quot;) is not supported by m2e. pom.xml	/jasperreports-test	line 60	Maven Project Build Lifecycle Mapping Problem

Why do I care if m2eclipse doesn&#39;t &quot;support&quot; this task? Maven does, and that&#39;s all I really care about. How can I get this error in my project to go away? 


maven-dependency-plugin (goals &quot;copy-dependencies&quot;, &quot;unpack&quot;) is not supported by m2e

Consider:

[![Enter image description here][1]][1]

When I create a simple [Maven][2] project in [Eclipse][3] I am getting this error:

&gt; web.xml is missing and `&lt;failOnMissingWebXml&gt;` is set to
&gt; true

How can I fix this problem?

  [1]: http://i.stack.imgur.com/Yd22p.png
  [2]: http://en.wikipedia.org/wiki/Apache_Maven
  [3]: http://en.wikipedia.org/wiki/Eclipse_%28software%29


web.xml is missing and &lt;failOnMissingWebXml&gt; is set to true

Maven2: Missing artifact but jars are in place

I would like to take advantage of the features that Maven provides for managing dependencies in a project. My brief understanding of how Maven works is that it will aquire the JARs needed and then build the project with these libraries.

Currently I have a simple POM file set up as a test:

    &lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot; 
    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
     xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd&quot;&gt;
      &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
      &lt;groupId&gt;com.jamesgoodwin.test&lt;/groupId&gt;
      &lt;artifactId&gt;com.jamesgoodwin.test&lt;/artifactId&gt;
      &lt;version&gt;0.0.1-SNAPSHOT&lt;/version&gt;
      &lt;build&gt;
      &lt;/build&gt;
      &lt;dependencies&gt;
      	&lt;dependency&gt;
      		&lt;groupId&gt;org.springframework&lt;/groupId&gt;
      		&lt;artifactId&gt;spring-core&lt;/artifactId&gt;
      		&lt;version&gt;3.0.0.RELEASE&lt;/version&gt;
      		&lt;type&gt;jar&lt;/type&gt;
      		&lt;scope&gt;compile&lt;/scope&gt;
      	&lt;/dependency&gt;
      &lt;/dependencies&gt;
    &lt;/project&gt;

To manage dependencies, I usually add the project or JAR to the build path and then i&#39;ll be able to build my project.. 

But when using **M2Eclipse** the dependencies are not added automatically to the build path. Is there any configuration to let Eclipse know that the Maven is managing the dependencies?

How to configure Eclipse build path to use Maven dependencies?

I am using Eclipse 3.7 Indigo with Maven M2E Plugin 1.0.100.

Using the JBoss 7.x JavaEE 6 EAR archetype, the pom for EAR is giving me this error:

&gt; Plugin execution not covered by lifecycle configuration:
&gt; org.apache.maven.plugins:maven-ear-plugin:2.6:generate-application-xml
&gt; (execution: default-generate-application-xml, phase:
&gt; generate-resources)

&lt;!-- language: lang-xml --&gt;

    &lt;plugin&gt;
       &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
       &lt;artifactId&gt;maven-ear-plugin&lt;/artifactId&gt;
       &lt;version&gt;2.6&lt;/version&gt;
       &lt;configuration&gt;
          &lt;!-- Tell Maven we are using Java EE 6 --&gt;
          &lt;version&gt;6&lt;/version&gt;
          &lt;!-- Use Java EE ear libraries as needed. Java EE ear libraries 
                      are in easy way to package any libraries needed in the ear, and automatically 
                      have any modules (EJB-JARs and WARs) use them --&gt;
          &lt;defaultLibBundleDir&gt;lib&lt;/defaultLibBundleDir&gt;
          &lt;modules&gt;&lt;/modules&gt;
       &lt;/configuration&gt;
    &lt;plugin&gt;

Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

 - Regarding *Eclipse IDE* (**Indigo**, **Juno** and **Kepler** (32 and 64 bit versions))
 - *Platforms*: **Windows**, **Ubuntu**, **Mac**
 - *m2e version*: **1.1.0.20120530-0009**, **1.2.0.20120903-1050**, **1.3.0.20130129-0926**,                
**1.4.0.20130601-0317**	

----------

**General info**
------------------------------

The above error came after updating the m2e to version 1.1. ***By removing m2e 1.1 and rolling back to m2e 1.0 everything worked fine.*** I tried to repeat the problem in Windows and Ubuntu and it gave me the exact same error. Numerous configurations of the slf4j-api and logback were tested but none seem to work. 

The error appears in any maven project **even without declaring slf4j dependency**. 

 - New Maven Project--&gt; maven-archetype-quickstart 

       **and** 

 - New Maven Project--&gt; Simple project without archetype selection 

   result to

   &lt;!-- language: java --&gt;

    SLF4J: Failed to load class &quot;org.slf4j.impl.StaticLoggerBinder&quot;.

----------

**Testing enviroments and configurations**
------------------------------
Tested with Eclipse Indigo and Eclipse Juno (32 and 64 bit both) on Mac, 32 bit on Ubuntu and 64 and 32 bit on Windows. Tested fresh installs of **Juno Classic**, **Juno Modelling tools**, **Kepler Standard**, **Kepler Modelling Tools** and produced the same error. 

The error appears with **clean**, **install**, **test**, **deploy**, **generate-sources**, **validate** , **compile** , **package**, **integration-test**, **verify** and combinations of the goal clean with the rest goals. It appears also with parameters **-e** and **-X**. There was an attempt to delete the m2e repository and download it from scratch but again without success. It should me mentioned that it was tested in 3 different machines and virtual box all the above systems but it produced the same error. 

Tried all different **logback** configurations (from 1.0.4 to 1.0.13) that resolve the **slf4j-api** and **logback-core** dependencies, but all produce the same error:

&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
       &lt;groupId&gt;ch.qos.logback&lt;/groupId&gt;
       &lt;artifactId&gt;logback-classic&lt;/artifactId&gt;
       &lt;version&gt;&lt;/version&gt;
    &lt;/dependency&gt;

Tried all different (from 1.6.1 to 1.7.5 ) **slf4j-simple** configurations.

&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
       &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
       &lt;artifactId&gt;slf4j-simple&lt;/artifactId&gt;
       &lt;version&gt;&lt;/version&gt;
       &lt;scope&gt;compile&lt;/scope&gt;
    &lt;/dependency&gt;

Tried all different (from 1.6.1 to 1.7.5 ) **log4j-over-slf4j** configurations.

&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
       &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
       &lt;artifactId&gt;log4j-over-slf4j&lt;/artifactId&gt;
       &lt;version&gt;&lt;/version&gt;
       &lt;scope&gt;compile&lt;/scope&gt;
    &lt;/dependency&gt;

Tried all different (from 1.6.1 to 1.7.5 ) **slf4j-jdk14** configurations.

&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
       &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
       &lt;artifactId&gt;slf4j-jdk14&lt;/artifactId&gt;
       &lt;version&gt;&lt;/version&gt;
       &lt;scope&gt;compile&lt;/scope&gt;
    &lt;/dependency&gt;

Tried all different (from 1.6.1 to 1.7.5 ) **slf4j-log4j12** configurations.


&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
         &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
         &lt;artifactId&gt;slf4j-log4j12&lt;/artifactId&gt;
         &lt;version&gt;&lt;/version&gt;
         &lt;scope&gt;compile&lt;/scope&gt;
    &lt;/dependency&gt;


Tried **slf4j-nop 1.7.5** configuration.


&lt;!-- language: xml --&gt;

    &lt;dependency&gt;
      &lt;groupId&gt;org.slf4j&lt;/groupId&gt;
      &lt;artifactId&gt;slf4j-nop&lt;/artifactId&gt;
      &lt;version&gt;1.7.5&lt;/version&gt;
      &lt;scope&gt;compile&lt;/scope&gt;
    &lt;/dependency&gt;


***Last but not least the logs are saved and printed despite the error.***


----------


**Ways to reproduce the error**
------------------------------

 - Download Eclipse Juno, Indigo or Kepler 32 or 64 bit (All installations will
   cause the same error). 
     - Install m2e - Maven Integration for Eclipse
         - Juno - http://download.eclipse.org/releases/juno
         - Kepler - http://download.eclipse.org/releases/kepler
         - Indigo - http://download.eclipse.org/technology/m2e/releases/ (***currently unavailable***)

        **OR**
 
     - Update your m2e version to **1.1.0.20120530-0009**, or **1.2.0.20120903-1050**, or **1.3.0.20130129-0926**, or **1.4.0.20130601-0317** )
&lt;hr&gt;
     - Select File-&gt;New-&gt;Other-&gt;Maven Project-&gt;Click Next-&gt;Select      
   maven-archetype-quickstart from the catalog-&gt;Finish
     
        **OR**

     - Select File-&gt;New-&gt;Other-&gt;Maven Project-&gt;Click Next-&gt;Select Create a simple project (skip archetype selection)-&gt; Complete Artifact info-&gt; Finish
 - Right Click on the project-&gt;Runs As-&gt;clean install (or any other goal mentioned above)

The first line on the console will be 

&lt;!-- language: java --&gt;

    SLF4J: Failed to load class &quot;org.slf4j.impl.StaticLoggerBinder&quot;.
    SLF4J: Defaulting to no-operation (NOP) logger implementation
    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.



***P.S. Existing projects will produce the same error after updating the m2e version to 1.1.0.20120530-0009***, **1.2.0.20120903-1050**, **1.3.0.20130129-0926**, **1.4.0.20130601-0317**

&lt;hr&gt;
**Updates**
------------------------------

**EDIT**

**m2e support site:** 

 - The above question was posted as a bug in m2e support site and the answer from Igor Fedorenko was that


       &gt; There are no immediate plans to suppress this message.

       For viewing the above bug please refer to [m2e official support site][1]

&lt;hr&gt;
**EDIT 2**

 - The above error indication is **present** also to **m2e** version ***1.2.0.20120903-1050***

&lt;hr&gt;
**EDIT 3**

 - The above error indication is **present** also to **m2e** version ***1.3.0.20130129-0926***


&lt;hr&gt;
**EDIT 4**

 - The above error indication is **present** also to **m2e** version ***1.4.0.20130601-0317***

&lt;hr&gt;
**EDIT 5**

             
                                  ***Reported FIXED***



 - The above error is reported as fixed for **m2e** version ***1.5.0/Luna M3***(*Target Milestone*). The version is not yet available for download. 
 - ***Luna M3*** is [scheduled for Nov. 15th][2]. 
 - Latest dev build are available [here][3]    
 - More information about the m2e milestones you can find at the [m2e main repository][4]. 


  [1]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=387064
  [2]: http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule
  [3]: http://nexus.tesla.io:8081/nexus/content/sites/m2e.extras/m2e/1.5.0/N/LATEST/
  [4]: http://git.eclipse.org/c/m2e/m2e-core.git/

SLF4J: Failed to load class &quot;org.slf4j.impl.StaticLoggerBinder&quot;. error

We have a project set up with maven for resolving dependancies. It usually works fine, but now I am trying to compile and run it on a new PC and I have problem with missing dependencies in Eclipse.

What is funny is that if I run &quot;mvn package&quot; in console or in eclipse, it works fine and even produces war containing all necessary jars. Only Eclipse complains with &quot;The project was not built since its build path is incomplete. Cannot find the class file for org.slf4j.Logger...&quot;. If I compare the project with some other computer (where project works fine), I notice that there are quite a few libraries missing under &quot;Maven dependencies&quot; listing in Eclipse. Eventhough they are in the packaged war and they can be found also under repository folder.

So, the jar-s are there just Eclipse won&#39;t list them all under &quot;Maven dependencies&quot;. What can I do?

Computer is running on Windows 7 with 64bit java &amp; eclipse.

Missing Maven dependencies in Eclipse project

I have a maven project in eclipse and have maven goals that run annotation processors to generate code. The output folder for this code is `target/generated-sources/apt`.

In order for Eclipse to see this generated code I need to add `target/generated-sources/apt` as a source folder to the Eclipse project.

However, this causes there to be an error of type &quot;Maven Configuration Problem&quot; saying

&gt; Project configuration is not up-to-date with `pom.xml`. Run project
&gt; configuration update

I think I understand why this is the case as Eclipse has a different set of source folders to Maven&#39;s set. But I need this different set, as I need Eclipse to be able to see the `generated` source folders...

When doing a pure Maven built, these source folders will be included in the build, by Maven.

BTW, I have upgraded to the official Eclipse release of the Maven Eclipse plugin, m2e 1.0 - what used to be m2eclipse. I&#39;d like to see if I can find a work around/solution to this with the m2e plugin before I have to go back to the old m2eclipse version.

M2E and having maven generated source folders as eclipse source folders

I&#39;m developing a Java EE web project. When I try to add a dependency, this error message appears. I use Eclipse Kepler.

&gt; An internal error occurred during: &quot;Updating Maven Project&quot;. java.lang.NullPointerException

Could you help me?
Thank you.

![enter image description here][1]


  [1]: http://i.stack.imgur.com/uGiOI.jpg

An internal error occurred during: &quot;Updating Maven Project&quot;. java.lang.NullPointerException

Assuming you&#39;re already using the [m2eclipse plugin][1], what can you do when it doesn&#39;t update the dependencies to the latest in your repo?

For example, on the command line, you can just add the `-U` flag as in

    mvn clean install -U 

…to force the dependencies to be updated. Is there something like this within Eclipse? (It doesn&#39;t always seem to pick up the latest updates.)

  [1]: http://m2eclipse.sonatype.org/

How to update maven repository in Eclipse?

I installed the [Maven][1] plugin for [Eclipse][2], and then I got an error like below:

&gt; please make sure the -vm option in eclipse.ini is pointing to a JDK

How do I use the `-vm` option to point to my JDK in eclipse.ini?

  [1]: http://en.wikipedia.org/wiki/Apache_Maven
  [2]: http://en.wikipedia.org/wiki/Eclipse_%28software%29


How do I set the eclipse.ini -vm option?

I have imported maven project in STS, when I run update update project I receive:


    &quot;Updating Maven Project&quot;. Unsupported IClasspathEntry kind=4

Is there a workaround for this?

How to fix error &quot;Updating Maven Project&quot;. Unsupported IClasspathEntry kind=4?

I am starting to configure my development environment and I am using Spring Tool Suite 2.8.1 along with m2E 1.01.

As far as I can tell, since this is a Maven Project (my first), my Maven POM is dictating (along with m2E smarts) my project build configuration and dependencies.

What I would like to know is why my IDE is displaying Java Build Problems that read &quot;Archive required for library *library/path/somejar.jar* cannot be read or is not a valid zip file&quot; when I can see the jars in my .m2 repository?

All the errors pertained to commons-logging:1.1.1 which I excluded in my parent-pom. This was a transistive dependancy via spring-context-support:3.0.5. I excluded that library from my build and now the errors pertain to the spring-context-support library.

I have attached a screenshot to illustrate.

![Markers][1]

  [1]: http://i.stack.imgur.com/0QfjQ.png



Compiler error &quot;archive for required library could not be read&quot; - Spring Tool Suite

I&#39;m trying to create a very simple webapp with maven and eclipse, but I&#39;m having no joy at all, in fact the reverse of joy.

I go to File -&gt; New Project, select Maven Project, and select the maven-archetype-webapp. When I finish the wizard, a webapp structure gets generated but with no &#39;java&#39; directory under main, just resources and webapp. 

So I right click on main and select new Class. The class gets created under resources (?!), and furthermore, there seems to be no compilation of it by java. I can make stupid errors and no syntax highlighting comes up. It&#39;s like java isn&#39;t recognizing it.

Alternatively I have tried creating a new &#39;java&#39; directory under main where it should be, but still with the same non-existent java symptoms.

What gives? This is driving me insane..

Thanks all!

maven-archetype-webapp eclipse problem

Eclipse&#39;s &quot;problems&quot; tab is displaying this error:

&gt; Description: Java compiler level does not match the version of the installed Java project facet.  
&gt; Resource: groupping  
&gt; Path: [blank]  
&gt; Location: Unknown  
&gt; Type: Faceted Project Problem (Java Version Mismatch)

My `pom.xml` has this setting:

    &lt;plugins&gt;
        &lt;plugin&gt;
            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
            &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
            &lt;configuration&gt;
                &lt;source&gt;1.6&lt;/source&gt;
                &lt;target&gt;1.6&lt;/target&gt;
            &lt;/configuration&gt;
        &lt;/plugin&gt;
    &lt;/plugins&gt;

Where else could the settings be mismatched?

&quot;Faceted Project Problem (Java Version Mismatch)&quot; error message

I am developing a web application with Eclipse and I generate the project with a maven archetype.

When I enable maven dependency management, Eclipse mark some errors in the pom file, this error is:

     Multiple annotations found at this line:
	- Execution default-testResources of goal org.apache.maven.plugins:maven-resources-          plugin:2.4.3:testResources failed: 
	 Plugin org.apache.maven.plugins:maven-resources-plugin:2.4.3 or one of its dependencies could not be resolved: Failed to collect 
	 dependencies for org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 () (org.apache.maven.plugins:maven-resources-
	 plugin:2.4.3:testResources:default-testResources:process-test-resources)
	- Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile 
	 (execution: default-compile, phase: compile)
	- CoreException: Could not get the value for parameter compilerId for plugin execution default-compile: 
	 PluginResolutionException: Plugin org.apache.maven.plugins:maven-compiler-plugin:2.3.2 or one of its dependencies could not be 
	 resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 (): 
	 ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.0.6: 
	 ArtifactResolutionException: Failure to transfer org.apache.maven:maven-plugin-api:pom:2.0.6 from http://repo1.maven.org/
	 maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or 
	 updates are forced. Original error: Could not transfer artifact org.apache.maven:maven-plugin-api:pom:2.0.6 from/to central (http://
	 repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0.6/maven-plugin-
	 api-2.0.6.pom
	- CoreException: Could not get the value for parameter compilerId for plugin execution default-testCompile: 
	 PluginResolutionException: Plugin org.apache.maven.plugins:maven-compiler-plugin:2.3.2 or one of its dependencies could not be 
	 resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 (): 
	 ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.0.6: 
	 ArtifactResolutionException: Failure to transfer org.apache.maven:maven-plugin-api:pom:2.0.6 from http://repo1.maven.org/
	 maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or 
	 updates are forced. Original error: Could not transfer artifact org.apache.maven:maven-plugin-api:pom:2.0.6 from/to central (http://
	 repo1.maven.org/maven2): null to http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0.6/maven-plugin-
	 api-2.0.6.pom
	- Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources failed: Plugin 
	 org.apache.maven.plugins:maven-resources-plugin:2.4.3 or one of its dependencies could not be resolved: Failed to collect 
	 dependencies for org.apache.maven.plugins:maven-resources-plugin:jar:2.4.3 () (org.apache.maven.plugins:maven-resources-
	 plugin:2.4.3:resources:default-resources:process-resources)
	- Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:
	 2.3.2:testCompile (execution: default-testCompile, phase: test-compile)
My pom file is the following:

&lt;!-- language: xml --&gt;

    &lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;                 xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
      xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd&quot;&gt;
       &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
       &lt;groupId&gt;com.lala.sarasa&lt;/groupId&gt;
       &lt;artifactId&gt;msrdecision&lt;/artifactId&gt;
      &lt;packaging&gt;war&lt;/packaging&gt;
      &lt;version&gt;1.0-SNAPSHOT&lt;/version&gt;
      &lt;name&gt;msrdecision Maven Webapp&lt;/name&gt;
      &lt;url&gt;http://maven.apache.org&lt;/url&gt;
     &lt;dependencies&gt;
       &lt;dependency&gt;
         &lt;groupId&gt;junit&lt;/groupId&gt;
          &lt;artifactId&gt;junit&lt;/artifactId&gt;
          &lt;version&gt;3.8.1&lt;/version&gt;
          &lt;scope&gt;test&lt;/scope&gt;
        &lt;/dependency&gt;
      &lt;/dependencies&gt;
      &lt;build&gt;
        &lt;finalName&gt;hello&lt;/finalName&gt;
       &lt;/build&gt;
     &lt;/project&gt;

Any idea?

m2eclipse error

With intent to get m2e 1.0 working correctly I have had to specify the lifecycle mapping:

		&lt;pluginManagement&gt;
			&lt;plugins&gt;
				&lt;plugin&gt;
					&lt;groupId&gt;org.eclipse.m2e&lt;/groupId&gt;
					&lt;artifactId&gt;lifecycle-mapping&lt;/artifactId&gt;
					&lt;version&gt;1.0.0&lt;/version&gt;
					&lt;configuration&gt;
						&lt;lifecycleMappingMetadata&gt;
							&lt;pluginExecutions&gt;
            					&lt;pluginExecution&gt;
              						&lt;pluginExecutionFilter&gt;
                						&lt;groupId&gt;org.bsc.maven&lt;/groupId&gt;
                						&lt;artifactId&gt;maven-processor-plugin&lt;/artifactId&gt;
                						&lt;versionRange&gt;[2.0.2,)&lt;/versionRange&gt;
                						&lt;goals&gt;
                  							&lt;goal&gt;process&lt;/goal&gt;
                						&lt;/goals&gt;
              						&lt;/pluginExecutionFilter&gt;
              						&lt;action&gt;
                						&lt;execute /&gt;
              						&lt;/action&gt;
            					&lt;/pluginExecution&gt;
            				&lt;/pluginExecutions&gt;         				
						&lt;/lifecycleMappingMetadata&gt;
					&lt;/configuration&gt;
				&lt;/plugin&gt;
			&lt;/plugins&gt;
		&lt;/pluginManagement&gt;


But then I get this warning:

     [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available
     [WARNING] Failed to retrieve plugin descriptor for org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0

if I run some specific maven task for example `mvn clean install findbugs:findbugs` (If I run only `mvn clean install` then there is no such message)

I know that the problem is that this POM does not exists, because it is only defined to hold the mapping information. ([https://stackoverflow.com/questions/7409823/m2e-lifecycle-mapping-not-found][1])

Anyway, I want to keep my build clean, without any warnings, so how can I get rid of this specific one? (*My CI server checks that there is no warning.*)

I use Maven 3.0.2 and tried Maven 3.0.3 too, but the same result.


  [1]: https://stackoverflow.com/questions/7409823/m2e-lifecycle-mapping-not-found

get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping

As the title mentioned I have the following problem: I use `Eclipse` with `Maven Nature` and when I update my Maven Project, I get this error:

&gt;An internal error occurred during: &quot;Updating Maven Project&quot;.  
    Unsupported IClasspathEntry kind=4

The solution that always comes back is the following:

 - rightclick project, remove maven nature
 - `mvn eclipse:clean` (with project open in eclipse/STS)
 - (sometimes they suggest to do `mvn eclipse:eclipse` next)
 - rightclick project and reenable maven nature

Now I exhaustively tried all combinations several times. But I always keep getting the above error. The error starting occurring when I had to `mvn eclipse:eclipse` the project. Before it was always running fine using only **m2eclipse** features and setting everything in eclipse.

An internal error occurred during: &quot;Updating Maven Project&quot;. Unsupported IClasspathEntry kind=4

In Eclipse Juno, I installed the latest m2e plugin (1.2.20120903-1050).  In preferences, I have added jdk1.7.0_11 in Java -&gt; Installed JREs -&gt; Add, and then specified the location (`C:\Program Files\Java\jdk1.7.0_11`).  When I create a new Maven project and run it, I get a warning:

&gt;Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment.

I am not sure how to resolve this.

I believe it is a Maven problem because I do not have this error when I run normal Java projects.  I read [here][1] that I should change the &quot;maven-compiler-plugin.pom&quot; and change the source and target from 1.5 to something more appropriate.  In my case, 1.7.  I have done this, but I still get the warning.

  [1]: http://mikechencodingnotes.blogspot.com/2011/11/m2e-compiler-j2se-15-warning-message.html

Maven &quot;build path specifies execution environment J2SE-1.5&quot;, even though I changed it to 1.7

Okay. I&#39;m sick of this problem.  This *has to* have an easy fix, I&#39;m sure of it!! I hope SO can help me to get rid of this once and for all!

&gt; **Question**
&gt; 
&gt; How do we get Eclipse to stop trying
&gt; to process/compile all files under a
&gt; particular project directory?  The
&gt; goal is for no errors/warnings to
&gt; exist in the problems view if they
&gt; relate to something in this folder or it&#39;s subfolders.

**Background**

We run Eclipse 3.6 and the m2eclipse plugin v0.10.2.20100623 manages our autobuild. For reasons beyond my control, we have the entire BlazeDS distribution in our SVN project directory under `src/main/resources/blazeds`.  Essentially, this directory contains a vanilla distribution of tomcat running blazeds to which all our configuration and project files are added when we deploy to our server via SCP.

So, when we run deploy, this version of tomcat is copied to the server and our project is placed inside.  Tomcat and our RIA application work and everything is fine.

The problem is, Eclipse tries to compile everything under `src/main/resources/blazeds` when running AutoBuild and this generates about 300 errors/warnings in our problem view.  So when a real error surfaces, it gets lost among the noise.

  The errors stem from code in `/blazeds/tomcat/webapps/samples/testdrive-datapush` and also the `testdrive-httpservice`, `traderdesktop` example webapps. They have dependent source code that&#39;s not on the classpath and jars that aren&#39;t included in the libraries.

**Failed Attempted Solutions**

I&#39;m trying to push the proper solution: to remove the samples completely and also to get blazeds out of our version control.  That&#39;s not happening anytime soon.

I&#39;ve followed the [SO answer here][1] but it&#39;s only a very temporary solution.  I&#39;ve tried adding exclusions everywhere I can think of and other members of my team have done the same.  I&#39;ve removed `src/main/resources` as a source directory (in preferences &gt; Java Build Path &gt; Source Tab) I&#39;ve added exclusions for `blazeds` under the resource directory.  I&#39;ve tried every permutation of `blazeds` and `**` as in `*blazeds*`, `**/blazeds/**`, etc.

I&#39;ve even tried including the libraries and source files the compiler is complaining about but I couldn&#39;t get it right without excessively mangling our project configuration.

&gt; **Summary**
&gt; 
&gt; This has to be simple. What is the
&gt; conventional way to exclude a folder
&gt; that is producing warnings/errors in
&gt; an eclipse project?
&gt;
&gt; &lt;hr&gt;
&gt; ***Update #1:*** &lt;br&gt;
&gt; gedim&#39;s solution below is decent but it&lt;br&gt;
&gt; 1) doesn&#39;t clear red X&#39;s from the project&lt;br&gt;
&gt; 2) is a change everyone on our team needs to do, manually&lt;br&gt;(i.e., it&#39;s not in a project property file; thereby, it isn&#39;t checked into subversion)&lt;br&gt;
&gt;&lt;br&gt;
&gt; I hope there&#39;s a way to address the core problem by telling Eclipse that this directory doesn&#39;t contain&lt;br&gt;
&gt; items to compile/validate. Such a change would likely show up in one of the project setting files.
&gt;

&lt;hr&gt;
**Update #2:**

The picture below shows the red X&#39;s I&#39;m trying to clear and that&lt;br&gt;
`Build Path &gt; Exclude` &lt;br&gt; isn&#39;t an option...

![Red X&#39;s won&#39;t go away][2]


  [1]: https://stackoverflow.com/questions/2514296/how-do-i-remove-error-warnings-made-by-tpl-files-in-my-eclipse-project
  [2]: http://i.stack.imgur.com/auYdR.gif

How to exclude a folder that is producing warnings/errors in an Eclipse project?

I have a problem with checkout Maven project in Eclipse Indigo. I&#39;ve installed m2e plugin, Subclipse, Git, but can&#39;t select appropriate SCM type ? How to solve this ?

![Checkout as Maven project from SCM][1]

  [1]: http://i.stack.imgur.com/5iFYk.jpg


Checkout Maven project from SCM - no connectors

I am trying to use the solution [described here][1] to solve the annoying &quot;Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (execution: default, phase: generate-sources)&quot; when I place the following plugin on my pom.xml:

    &lt;plugin&gt;
    &lt;groupId&gt;org.codehaus.mojo&lt;/groupId&gt;
    &lt;artifactId&gt;build-helper-maven-plugin&lt;/artifactId&gt;
    &lt;executions&gt;
        &lt;execution&gt;
            &lt;phase&gt;generate-sources&lt;/phase&gt;
            &lt;goals&gt;&lt;goal&gt;add-source&lt;/goal&gt;&lt;/goals&gt;
            &lt;configuration&gt;
                &lt;sources&gt;
                    &lt;source&gt;src/bootstrap/java&lt;/source&gt;
                &lt;/sources&gt;
            &lt;/configuration&gt;
        &lt;/execution&gt;
    &lt;/executions&gt;
	&lt;/plugin&gt;

But when I run mvn clean install I get this:

Reason: POM &#39;org.eclipse.m2e:lifecycle-mapping&#39; not found in repository: Unable to download the artifact from any repository

Does anyone have a clue on how to make m2e and maven happy?

[1]:https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html

All M2eclipse Solutions on Gang of Coders

Total of 34 M2eclipse Solutions

Eclipse does not recognize content of persistence.xml

Eclipse loops endlessly: Invoking 'Maven Project Builder'

How to configure maven install to skip tests in eclipse?

How to deal with missing src/test/java source folder in Android/Maven project?

Version 1.8 of project facet java does not exist

How to solve "Plugin execution not covered by lifecycle configuration" for Spring Data Maven Builds

Java compiler level does not match the version of the installed Java project facet

What causes imported Maven project in Eclipse to use Java 1.5 instead of Java 1.6 by default and how can I ensure it doesn't?

Maven "Module" vs "Project" (Eclipse, m2eclipse plugin)

Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved

Maven: best way of linking custom external JAR to my project?

No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?

maven-dependency-plugin (goals "copy-dependencies", "unpack") is not supported by m2e

web.xml is missing and <failOnMissingWebXml> is set to true

Maven2: Missing artifact but jars are in place

How to configure Eclipse build path to use Maven dependencies?

Plugin execution not covered by lifecycle configuration (JBossas 7 EAR archetype)

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". error

Missing Maven dependencies in Eclipse project

M2E and having maven generated source folders as eclipse source folders

An internal error occurred during: "Updating Maven Project". java.lang.NullPointerException

How to update maven repository in Eclipse?

How do I set the eclipse.ini -vm option?

How to fix error "Updating Maven Project". Unsupported IClasspathEntry kind=4?

Compiler error "archive for required library could not be read" - Spring Tool Suite

maven-archetype-webapp eclipse problem

"Faceted Project Problem (Java Version Mismatch)" error message

m2eclipse error

get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping

An internal error occurred during: "Updating Maven Project". Unsupported IClasspathEntry kind=4

Maven "build path specifies execution environment J2SE-1.5", even though I changed it to 1.7

How to exclude a folder that is producing warnings/errors in an Eclipse project?

Checkout Maven project from SCM - no connectors

m2e lifecycle-mapping not found