如何解决Spring Data Maven构建的“不包括生命周期配置的插件执行”?

I am trying to work with Spring Data and Neo4j. I started by trying to follow this guide linked to by the main site. In particular I based my pom.xml off of the "Hello, World!" example file. Here is a snip from my pom.xml for the plugin that is causing the issues...

我正在尝试使用Spring Data和Neo4j。我开始尝试跟随主站点链接的指南。特别是我的pom。xml从“Hello, World!”示例文件中删除。这是我的pom。导致问题的插件的xml…

<plugin>
<!-- Required to resolve aspectj-enhanced class features -->
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>aspectj-maven-plugin</artifactId>
    <version>1.0</version>
    <configuration>
        <outxml>true</outxml>
        <aspectLibraries>
            <aspectLibrary>
                <groupId>org.springframework</groupId>
                <artifactId>spring-aspects</artifactId>
            </aspectLibrary>
            <aspectLibrary>
                <groupId>org.springframework.data</groupId>
                <artifactId>spring-data-neo4j</artifactId>
            </aspectLibrary>
        </aspectLibraries>
        <source>1.6</source>
        <target>1.6</target>
    </configuration>
    <executions>
        <!-- ERROR HERE IN ECLIPSE SEE BELOW FOR FULL MESSAGE -->
        <execution>
            <goals>
                <goal>compile</goal>
                <goal>test-compile</goal>
            </goals>
        </execution>
    </executions>
    <dependencies>
        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjrt</artifactId>
            <version>${aspectj.version}</version>
        </dependency>
        <dependency>
            <groupId>org.aspectj</groupId>
            <artifactId>aspectjtools</artifactId>
            <version>${aspectj.version}</version>
        </dependency>
    </dependencies>
</plugin>

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'm not a Maven expert, so please be very explanatory in your answers if possible.

我正在运行Eclipse 3.6.2和m2e0.13。我不是专家专家，所以如果可能的话，请尽可能解释清楚。

I've also tried m2e 1.0.0 via this update site and still get the same error.

我还通过这个更新站点尝试了m2e1.0.0，但仍然有相同的错误。

34 个解决方案

#1

In my case of a similar problem, instead of using Andrew's suggestion for the fix, it worked simply after I introduced <pluginManagement> tag to the pom.xml in question. Looks like that error is due to a missing <pluginManagement> tag. So, in order to avoid the exceptions in Eclipse, looks like one needs to simply enclose all the plugin tags inside a <pluginManagement> tag, like so:

在我遇到类似的问题时，我没有使用Andrew的修复建议，而是在我将 标签引入pom之后。xml的问题。看起来这个错误是由于缺少 标签。因此，为了避免在Eclipse中出现异常，看起来需要简单地将所有的插件标记封装在一个 标签内，就像这样:

<build>
    <pluginManagement>
        <plugins>
            <plugin> ... </plugin>
            <plugin> ... </plugin>
                  ....
        </plugins>
    </pluginManagement>
</build>

Once this structure is in place, the error goes away.

一旦这个结构就位，错误就会消失。

#2

What a mess. I don't remember where I found this but I had to add the following to get M2Eclipse to be happy. Even more sad is that it isn't exactly easy to understand why this tag is needed.

真是一团糟。我不记得我在哪里找到的，但是我必须添加下面的内容来让M2Eclipse感到高兴。更可悲的是，要理解为什么需要这个标签并不容易。

<build>
      ... various plugins ...

      <pluginManagement>
        <plugins>
            <!--This plugin's configuration is used to store Eclipse 
                m2e settings only. It has no influence on the Maven build itself. -->
            <plugin>
                <groupId>org.eclipse.m2e</groupId>
                <artifactId>lifecycle-mapping</artifactId>
                <version>1.0.0</version>
                <configuration>
                    <lifecycleMappingMetadata>
                        <pluginExecutions>
                            <pluginExecution>
                                <pluginExecutionFilter>
                                    <groupId>org.codehaus.mojo</groupId>
                                    <artifactId>aspectj-maven-plugin</artifactId>
                                    <versionRange>[1.0,)</versionRange>
                                    <goals>
                                        <goal>test-compile</goal>
                                        <goal>compile</goal>
                                    </goals>
                                </pluginExecutionFilter>
                                <action>
                                    <execute />
                                </action>
                            </pluginExecution>
                        </pluginExecutions>
                    </lifecycleMappingMetadata>
                </configuration>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

There were a number of other issues with the M2Eclipse plug-in that simply didn't work with Spring Data. In the end I disabled M2Eclipse in favor of the Apache Eclipse plug-in.

M2Eclipse插件还存在许多其他问题，这些问题根本无法与Spring数据一起工作。最后，我禁用了M2Eclipse，转而支持Apache Eclipse插件。

#3

Quickest way to solve this is (from Eclipse m2e documentation):

解决这一问题的最快方法是(从Eclipse m2e文档):

1. use quick-fix on the error in pom.xml and select Permanently mark goal run in pom.xml as ignored in Eclipse build - this will generate the required boilerplate code for you.

   使用快速修正pom的错误。xml并选择永久标记目标在pom中运行。在Eclipse构建中忽略了xml——这将为您生成所需的样板代码。

2. After that just replace the <ignore/> tag with <execute/> tag in the generated configuration and you're done:

   在这之后，只需在生成的配置中替换 标记和 标记，您就完成了:

   <action>
       <execute/>
   </action>
   

#4

In Eclipse Luna 4.4.0, you can chose to ignore this error in preferences

在Eclipse Luna 4.4.0中，您可以选择忽略该错误的首选项。

Window > Preferences > Maven > Errors/Warnings > Plugin executiuon not covered by lifecycle configuration. Select Ignore / Warninig / Error as you wish.

窗口>偏好> Maven >错误/警告>插件执行不包括生命周期配置。如您所愿，选择忽略/ Warninig / Error。

Also, In the quick fix (Ctrl + 1) for this error, it gives an option to Mark goal as ignored in Eclipse build in Eclipse preferences (experimental)

此外，在快速修复(Ctrl + 1)中，它提供了一个选项，可以在Eclipse构建的Eclipse首选项(实验)中忽略目标。

This is a cleaner way, as it doesn't modify your pom.xml.

这是一种更干净的方法，因为它不会修改您的pom.xml。

You will need to do a Maven > Update project to fix the same error in any other project as well.

您需要做一个Maven >更新项目来修复其他项目中同样的错误。

#5

See https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html .

见https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html。

To solve some long-standing issues, m2e 1.0 requires explicit instructions what to do with all Maven plugins bound to "interesting" phases of project build lifecycle. We call these instructions "project build lifecycle mapping" or simply "lifecycle mapping" because they define how m2e maps information from project pom.xml file to Eclipse workspace project configuration and behaviour during Eclipse workspace build.

为了解决一些长期存在的问题，m2e 1.0需要明确的指示，如何处理与项目构建生命周期“有趣”阶段相关的所有Maven插件。我们将这些指令称为“项目构建生命周期映射”或简单的“生命周期映射”，因为它们定义了m2e从项目pom中映射信息的方式。在Eclipse工作空间构建过程中，xml文件到Eclipse工作区项目配置和行为。

Project build lifecycle mapping configuration can be specified in project pom.xml, contributed by Eclipse plugins and there is also default configuration for some commonly used Maven plugins shipped with m2e. We call these "lifecycle mapping metadata sources". m2e will create error marker like below for all plugin executions that do not have lifecycle mapping in any of the mapping metadata sources.

项目构建生命周期映射配置可以在项目pom中指定。由Eclipse插件提供的xml，还有一些常用的m2e附带的Maven插件的默认配置。我们称之为“生命周期映射元数据源”。m2e将为所有在映射元数据源中没有生命周期映射的插件执行创建如下的错误标记。

Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-antrun-plugin:1.3:run
   (execution: generate-sources-input, phase: generate-sources)

m2e matches plugin executions to actions using combination of plugin groupId, artifactId, version range and goal. There are three basic actions that m2e can be instructed to do with a plugin execution -- ignore, execute and delegate to a project configurator.

m2e匹配插件的执行，使用插件组群、artifactId、版本范围和目标的组合。m2e可以通过三种基本操作来指导插件执行——忽略、执行和委托给一个项目配置程序。

#6

m2e 0.13 introduce a m2e connectors and m2e Market Place to extend m2e features. It's like the old m2e-extras repository.

m2e 0.13引入了m2e连接器和m2e市场空间来扩展m2e特性。它就像旧的m2e-extras存储库。

You can access the m2e market place from the preferences: Preferences>Maven>Discovery>Open Catalog. Installing WTP integration solved most plugin issues for me.

您可以从首选项访问m2e市场位置:首选项>Maven>发现>开放目录。安装WTP集成解决了我的大多数插件问题。

#7

As an addendum to the previous answers -- there's a workaround I just discovered for if you can't or don't want to add all this boilerplate to your project POM. If you look in the following location:

作为前面答案的附录——我刚刚发现了一个解决方案，如果您不能或不想将所有这些样板文件添加到项目POM中。如果你看以下地点:

{Eclipse_folder}/plugins/org.eclipse.m2e.lifecyclemapping.defaults_{m2e_version}

You should find a file called lifecycle-mapping-metadata.xml where you can make the same changes described in the other answers and in M2E plugin execution not covered.

您应该找到一个名为lifecycle-mappingmetadata的文件。在xml中，您可以在其他答案中进行相同的更改，并且在M2E插件的执行中没有涉及到。

#8

Note that the M2Eclipse (m2e) version 1.7.0 available in today's Eclipse Neon release train supports new syntax for specifying lifecycle mapping metadata. As a result boilerplate like this (here we're telling m2e to ignore the goal):

请注意，在今天的Eclipse霓虹灯发行版中，M2Eclipse (m2e)版本1.7.0提供了用于指定生命周期映射元数据的新语法。因此，像这样的样板文件(这里我们告诉m2e忽略目标):

<pluginManagement>
  <plugins>
    <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
    <plugin>
      <groupId>org.eclipse.m2e</groupId>
      <artifactId>lifecycle-mapping</artifactId>
      <version>1.0.0</version>
      <configuration>
        <lifecycleMappingMetadata>
          <pluginExecutions>
            <pluginExecution>
              <pluginExecutionFilter>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>exec-maven-plugin</artifactId>
                <versionRange>[1.5.0,)</versionRange>
                <goals>
                  <goal>exec</goal>
                </goals>
              </pluginExecutionFilter>
              <action>
                <ignore></ignore>
              </action>
            </pluginExecution>
          </pluginExecutions>
        </lifecycleMappingMetadata>
      </configuration>
    </plugin>
  </plugins>
</pluginManagement>

can be replaced with a single line in the plugin's execution node:

可以在插件的执行节点中替换为一行:

<?m2e ignore?>

See the release notes for details.

有关详细信息，请参阅发行说明。

#9

I had the same problem with Eclipse v3.7 (Indigo) and m2eclipse as my Maven plugin. The error was easily solved by explicitly stating the execution phase within the plugin definition. So my pom looks like this:

我在Eclipse v3.7 (Indigo)和m2eclipse中遇到了与Maven插件相同的问题。通过在插件定义中显式地声明执行阶段，可以很容易地解决这个错误。我的pom是这样的

<project>
    ...
    <build>
        ...
        <plugins>
            <plugin>

                <groupId>org.codehaus.mojo</groupId>
                <artifactId>buildnumber-maven-plugin</artifactId>
                <version>1.0</version>

                <configuration>
                    <timestampFormat>yyyy-MM-dd_HH-mm-ss</timestampFormat>
                </configuration>

                <executions>
                    <execution>
                        *<phase>post-clean</phase>*
                        <goals>
                            <goal>create-timestamp</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
        ...

#10

Change the Maven preferences for plugin execution from error to ignore

更改插件执行的Maven首选项，使其不受错误的影响。

#11

1. Go to Help > Install New Software...
2. 去帮助>安装新软件…

3. Use this software repository

   使用这个软件资源库

   Make sure "Contact all update sites during install to find required software" is checked.

   确保“在安装过程中联系所有更新站点以查找所需的软件”。

4. Install the AJDT m2e Configurator

   安装AJDT m2e配置器。

Source: Upgrading Maven integration for SpringSource Tool Suite 2.8.0 (Andrew Eisenberg)

源代码:为SpringSource工具套件2.8.0升级Maven集成(Andrew Eisenberg)

This should automatically install ADJT if you don't have it installed, but if it doesn't, install AspectJ Development Tools (ADJT) first from "Indigo update site" (according to your Eclipse version).

如果你没有安装它，它应该自动安装，但是如果它没有安装，那么首先从“Indigo更新站点”(根据您的Eclipse版本)安装AspectJ开发工具(ADJT)。

More info on AspectJ Development Tools site.

有关AspectJ开发工具站点的更多信息。

#12

I've had the same problem with indigo and a project that needs to generate Java sources from XSD.
I could fix it by supplying the missing life cycle mapping, as described on this page

我在indigo上遇到了同样的问题，还有一个项目需要从XSD生成Java源。我可以通过提供缺失的生命周期映射来修复它，正如这一页所描述的那样。

#13

Goto workspace/rtc-ws/.metadata/.plugins/org.eclipse.m2e.core/lifecycle-mapping-metadata.xml then create lifecycle-mapping-metadata.xml file and paste below and reload configuration as below

转到工作区/ rtc-ws / . metadata / . plugins / org.eclipse.m2e.core / lifecycle-mapping-metadata。xml然后创建lifecycle-mapping-metadata。xml文件和粘贴在下面和重新加载配置如下。

If you are using Eclipse 4.2 and have troubles with mapping and won't put mess into yours pom.xml create new file lifecycle-mapping-metadata.xml configure it in Windows -> Preferences -> Lifecycle mapping (don't forget press Reload workspace lifecycle mappings metadata after each change of this file!). Here is example based on eclipse/plugins/org.eclipse.m2e.lifecyclemapping.defaults_1.2.0.20120903-1050.jar/lifecycle-mapping-metadata.xml

如果您使用的是Eclipse 4.2，并且在映射上有问题，并且不会将混乱放到您的pom中。xml创建新的文件生命周期-映射-元数据。xml在Windows ->首选项->的生命周期映射中配置它(不要忘记在每次更改文件后重新加载工作区生命周期映射元数据!)下面是基于eclipse/plugins/org.eclipse.m2e. lifecyclemapp. defaults_1.2.0.20120903-1050.jar/ lifecycle-mappingmetadata.xml的例子。

<?xml version="1.0" encoding="UTF-8"?>
<lifecycleMappingMetadata>
    <pluginExecutions>
        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>buildnumber-maven-plugin</artifactId>
                <goals>
                    <goal>create-timestamp</goal>
                </goals>
                <versionRange>[0.0,)</versionRange>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <goals>
                    <goal>list</goal>
                </goals>
                <versionRange>[0.0,)</versionRange>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.zeroturnaround</groupId>
                <artifactId>jrebel-maven-plugin</artifactId>
                <goals>
                    <goal>generate</goal>
                </goals>
                <versionRange>[0.0,)</versionRange>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>gwt-maven-plugin</artifactId>
                <goals>
                    <goal>compile</goal>
                </goals>
                <versionRange>[0.0,)</versionRange>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
                <goals>
                    <goal>copy-dependencies</goal>
                    <goal>unpack</goal>
                </goals>
                <versionRange>[0.0,)</versionRange>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-antrun-plugin</artifactId>
                <versionRange>[1.7,)</versionRange>
                <goals>
                    <goal>run</goal>
                </goals>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>


        <pluginExecution>
            <pluginExecutionFilter>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-checkstyle-plugin</artifactId>
                <versionRange>[2.8,)</versionRange>
                <goals>
                    <goal>check</goal>
                </goals>
            </pluginExecutionFilter>
            <action>
                <ignore />
            </action>
        </pluginExecution>

    </pluginExecutions>
</lifecycleMappingMetadata>

#14

I fixed it following blog post Upgrading Maven integration for SpringSource Tool Suite 2.8.0.

我在博客后修复了SpringSource工具套件2.8.0的Maven集成。

Follow the advice on the section called "Uh oh…my projects no longer build". Even when it's intended for SpringSource Tool Suite I used it to fix a regular Eclipse installation. I didn't have to modify my pom files.

遵循“Uh oh…my projects no longer build”这一节的建议。甚至当它打算用于SpringSource工具套件时，我也使用它来修复一个常规的Eclipse安装。我不需要修改我的pom文件。

#15

Use m2e 0.12, last version from Sonatype.

使用Sonatype的最后一个版本m2e0.12。

#16

I was using

我用

<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.6</version>
<executions>
    <execution>
        <id>runSomeAntTasks</id>
        <phase>test-compile</phase>
        .
        .
        <goals>
            <goal>run</goal>
        </goals>
    </execution>
</executions>

and changed it to

并改变了

<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.6</version>
<executions>
<execution>
    <id>runSomeAntTasks</id>
    <phase>integration-test</phase>
        .
        .

        <goals>
            <goal>run</goal>
        </goals>
    </execution>
</executions>

and the error went away. Maybe it's not recommended to bind an execution to the test-compile phase so finding a different phase might be an alternate solution to adding plugin-management configuration to the maven lifecycle.

误差消失了。也许不建议将执行绑定到测试编译阶段，因此找到一个不同的阶段可能是在maven生命周期中添加插件管理配置的替代方案。

#17

Where find WTP:

找到WTP的地方:

Mouse down on < plugin > in pom.xml and 'Discover new m2e connectors'.

鼠标在pom中的< plugin >。xml和“发现新的m2e连接器”。

I installed them all what are default checked and it works.

我安装了所有默认的校验和它的工作。

#18

I had the exact same problem after updating m2e and solved it by reinstalling Maven Integration for Eclipse WTP.

在更新m2e并通过重新安装Eclipse WTP的Maven集成解决了这个问题后，我遇到了同样的问题。

As it turns out, I uninstalled it trying to update m2e from version 0.x to 1.x

结果是，我卸载了它试图从0版本更新m2e。x 1.倍

#19

This error happens also on neon because of missing m2e connector. Solution: hover error and select - Discover new m2e connectors.

由于缺少m2e连接器，这个错误也会发生在氖上。解决方案:悬停错误和选择-发现新的m2e连接器。

It will install new connector and that is it.

它将安装新的连接器，就是这样。

#20

I had this problem today. I was using STS 3.4 with its bundled Roo 1.2.4. Later I tried with Eclipse Kepler and Roo 1.2.5, same error.

我今天遇到了这个问题。我使用的是STS 3.4，其捆绑的Roo 1.2.4。后来我尝试了Eclipse Kepler和Roo 1.2.5，同样的错误。

I've changed my pom.xml adding pluginTemplates tag after build and before plugins declaration but didn't work.

我改变了我的砰的一声。在构建后和在插件声明之前添加插件标签，但是没有起作用。

What made the magic for me:

是什么让我变得如此神奇:

• Using jdk 1.7.0_51
• 使用jdk 1.7.0_51
• Downloaded Roo 1.2.5
• Roo 1.2.5下载
• Downloaded Maven 3.2.1 (if not, when executes "perform eclipse" this error appears "error=2, no such file or directory")
• 下载Maven 3.2.1(如果不是，当执行“执行eclipse”时，这个错误出现“error=2，没有这样的文件或目录”)

• Configured JDK, Roo and Maven bin directories on my PATH:

  在我的路径上配置了JDK、Roo和Maven bin目录:

  export PATH=/opt/jdk1.7.0_51/bin:$PATH export PATH=/opt/spring-roo-1.2.5.RELEASE/bin:$PATH export PATH=/opt/apache-maven-3.2.1/bin:$PATH

  导出路径= / opt / jdk1.7.0_51 / bin:路径导出路径= / opt / spring-roo-1.2.5美元。发布/ bin:$路径导出路径= / opt / apache-maven-3.2.1 / bin:美元的道路

Made my configuration as following: (http://docs.spring.io/spring-roo/reference/html/beginning.html)

使我的配置如下:(http://docs.spring.io/spring-roo/reference/html/beginning.html)

$ mkdir hello 
$ cd hello
$ roo.sh
roo> project --topLevelPackage com.foo
roo> jpa setup --provider HIBERNATE --database HYPERSONIC_PERSISTENT 
roo> web mvc setup
roo> perform eclipse

Open with Eclipse (nothing of STS, but I guess it works): Import -> Existing Projects into Workspace

打开Eclipse(没有任何STS，但我想它是可行的):将现有的项目导入到工作区中。

#21

Instead of messing up your pom file, I would suggest you to go to Show View → Markers in Eclipse, select and delete the markers of appropriate errors.

我建议您在Eclipse中显示视图标记，选择并删除适当错误的标记，而不是把pom文件弄乱。

#22

If you are using Eclipse Juno, it could be the issue of Maven Integration For Eclipse WTP . So install the same from Eclipse Market Place.

如果您使用的是Eclipse Juno，那么它可能是Eclipse WTP的Maven集成问题。所以在Eclipse市场上安装相同的软件。

In Eclipse IDE Help>>Eclipse Market Place >> type the query wtp and it will show maven integration for eclipse WTP for Juno, install it and update the maven dependencies and enjoy

在Eclipse IDE帮助>>Eclipse市场>>类型的查询wtp和它将显示maven集成的Eclipse wtp为Juno，安装它和更新maven依赖和享受。

#23

I encountered exact the same problem with maven thrift plugin. Here's my solution which requires no need to mess up your pom.xml:

我也遇到过同样的问题。这是我的解决方案，不需要弄乱你的。xml:

1. Use command line maven utility mvn

   使用命令行maven实用工具mvn。

   mvn eclipse:eclipse

   mvn eclipse:月食

   to create a eclipse project

   创建一个eclipse项目。

2. Import the project in eclipse. Remember to use

   在eclipse中导入项目。记住要使用

   File > Import > General > Existing Projects into Workspace

   文件>导入>通用>现有项目到工作区。

   to add the project into your workspace.

   将项目添加到您的工作空间中。

This should fix the problem.

这应该能解决问题。

#24

I got the same error. After doing the following it went away.

我犯了同样的错误。做完之后，它就消失了。

1. Right click on the project.
2. 右键单击项目。
3. Select Maven > Update Project...
4. 选择Maven >更新项目…

#25

This answer is just as good the top plugin-management answer above (which is to say, it's terrible).

这个答案和上面的顶部插件管理答案一样好(也就是说，它很糟糕)。

Just delete all the offending xml code in the pom.

只需删除pom中所有违规的xml代码。

Done. Problem solved (except you just broke your maven config...).

完成了。问题解决了(除了您刚刚打破了您的maven配置…)。

Devs should be very careful they understand plugin-management tags before doing any of these solutions. Just slapping plugin-management around your plugins are random is likely to break the maven build for everyone else just to get eclipse to work.

在使用这些解决方案之前，Devs应该非常仔细地理解插件管理标签。仅仅在您的插件上随意地使用插件管理是很有可能的，这可能会破坏maven的构建，而只是为了让eclipse工作。

#26

you can suppress this error in eclipse: Window -> Preferences -> Maven -> Error/Warnings

您可以在eclipse中抑制此错误:窗口->首选项-> Maven ->错误/警告。

#27

Changing

改变

<artifactId>aspectj-maven-plugin</artifactId>
<version>1.2</version>

into

成

<artifactId>aspectj-maven-plugin</artifactId>
<version>1.3</version>

solved the problem for me.

帮我解决了这个问题。

#28

I followed the GUI hint to finding any connector, and then I found AspectJ Integrator from SpringSource Team. After installation it was settled.

我按照GUI提示找到了任何连接器，然后我找到了SpringSource团队的AspectJ集成器。安装完毕后。

#29

I encountered this using Eclipse v4.3 (Kepler) and Maven 3.1.

我使用的是Eclipse v4.3 (Kepler)和Maven 3.1。

The solution is to use a JDK and not a JRE for your Eclipse project. Make sure to try maven clean and test from Eclipse just to download missing JAR files.

解决方案是使用JDK，而不是为您的Eclipse项目使用JRE。确保从Eclipse中尝试maven的清洁和测试，以下载丢失的JAR文件。

#30

For me this was caused by AspectJ classes. I could not find a plugin under Discovery that could help. So, I fixed this by copying the org.maven.ide.eclipse.ajdt files, under plugin and feature folders, of an existing STS installation.

对我来说，这是由AspectJ类造成的。我找不到一个可以帮助发现的插件。因此，我通过复制org.maven.ide.eclipse来修复它。ajdt文件，在插件和特征文件夹下，一个现有的STS安装。

I know, very rude approach.

我知道，非常粗鲁。