简体   繁体   English

这个Maven错误是什么? “生命周期配置未涵盖插件执行......”

[英]What is this Maven error ? “Plugin execution not covered by lifecycle configuration…)”

"Plugin execution not covered by lifecycle configuration: com.soebes.maven.plugins:iterator-maven-plugin: 0.4:iterator (execution: javascript-dependencies_unpack-dependencies, phase: initialize)" “生命周期配置未涵盖插件执行:com.soebes.maven.plugins:iterator-maven-plugin:0.4:iterator(执行:javascript-dependencies_unpack-dependencies,阶段:初始化)”

Trying to build Pentaho projects at https://github.com/pentaho . 尝试在https://github.com/pentaho上构建Pentaho项目。 None of them will build except maven-parent-poms at https://github.com/pentaho/maven-parent-poms . https://github.com/pentaho/maven-parent-poms中,除了maven-parent-poms之外,它们都不会构建。 Almost every other project throws this error in the corresponding .pom file. 几乎所有其他项目都会在相应的.pom文件中抛出此错误。 Refer to the screen snip, below, for the location of the error. 有关错误的位置,请参阅下面的屏幕截图。

I did override the Eclipse Maven extension with the current version of Maven from Apache. 我确实用Apache的当前版本的Maven覆盖了Eclipse Maven扩展。 Didn't change anything. 没有改变什么。

<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>pentaho</groupId>
    <artifactId>pentaho-platform-ce-parent</artifactId>
    <version>8.0-SNAPSHOT</version>
  </parent>
  <artifactId>pentaho-platform-api</artifactId>
  <version>8.0-SNAPSHOT</version>
  <properties>
    <maven-surefire-plugin.reuseForks>false</maven-surefire-plugin.reuseForks>
    <mockito-all.version>1.8.5</mockito-all.version>
    <license.header.definition.file>${basedir}/../license/styles/javadoc_style_license_header.xml</license.header.definition.file>
    <commons-lang.version>2.4</commons-lang.version>
    <license.header.file>${basedir}/../license/templates/LGPL-2.1.txt</license.header.file>
  </properties>
  <dependencies>
    <dependency>
      <groupId>commons-logging</groupId>
      <artifactId>commons-logging</artifactId>
      <version>${commons-logging.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>commons-lang</groupId>
      <artifactId>commons-lang</artifactId>
      <version>${commons-lang.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>dom4j</groupId>
      <artifactId>dom4j</artifactId>
      <version>${dom4j.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.springframework.security</groupId>
      <artifactId>spring-security-core</artifactId>
      <version>${spring.security.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-beans</artifactId>
      <version>${spring.framework.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-api</artifactId>
      <version>${slf4j-api.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>pentaho</groupId>
      <artifactId>pentaho-connections</artifactId>
      <version>${project.version}</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>pentaho</groupId>
      <artifactId>pentaho-actionsequence-dom</artifactId>
      <version>${project.version}</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>pentaho</groupId>
      <artifactId>pentaho-xul-core</artifactId>
      <version>${project.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>pentaho</groupId>
      <artifactId>pentaho-database-model</artifactId>
      <version>${project.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>pentaho</groupId>
      <artifactId>pentaho-service-coordinator</artifactId>
      <version>${project.version}</version>
      <scope>compile</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>${junit.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.mockito</groupId>
      <artifactId>mockito-all</artifactId>
      <version>${mockito-all.version}</version>
      <scope>test</scope>
      <exclusions>
        <exclusion>
          <artifactId>*</artifactId>
          <groupId>*</groupId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>
  <build>
    <plugins>
      <plugin>
        <groupId>com.mycila</groupId>
        <artifactId>license-maven-plugin</artifactId>
      </plugin>
    </plugins>
  </build>
</project>

在此输入图像描述

The problem is related to Eclipse M2E where you need to tell Eclipse that it should for example ignore the plugin etc. 问题与Eclipse M2E有关 ,你需要告诉Eclipse它应该例如忽略插件等。

<pluginManagement>
  <plugins>
    <plugin>
     <groupId>org.eclipse.m2e</groupId>
     <artifactId>lifecycle-mapping</artifactId>
     <version>1.0.0</version>
     <configuration>
       <lifecycleMappingMetadata>
         <pluginExecutions>
           <pluginExecution>
             <pluginExecutionFilter>
               <groupId>some-group-id</groupId>
               <artifactId>some-artifact-id</artifactId>
               <versionRange>[1.0.0,)</versionRange>
               <goals>
                 <goal>some-goal</goal>
               </goals>
             </pluginExecutionFilter>
             <action>
               <ignore/>
             </action>
           </pluginExecution>
         </pluginExecutions>
       </lifecycleMappingMetadata>
     </configuration>
    </plugin>
  </plugins>
</pluginManagement>

This is the old way of doing this. 这是执行此操作的旧方法。 There is newer way since 1.7 of m2e : 自m2e 1.7以来有更新的方式:

You can include the ignore etc. directly into the configuration of the execution: 您可以将ignore等直接包含在执行配置中:

<?m2e ignore?> 
<?m2e execute?>
<?m2e execute onConfiguration?> 
<?m2e execute onIncremental?> 
<?m2e execute onConfiguration,onIncremental?> 
<?m2e configurator configuratorId?> 

For example: 例如:

  <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>flatten-maven-plugin</artifactId>
        <version>1.0.0</version>
        <configuration>
          <updatePomFile>true</updatePomFile>
        </configuration>
        <executions>
          <execution>
            <?m2e ignore?>
            <id>flatten</id>
            <phase>process-resources</phase>
            <goals>
              <goal>flatten</goal>
            </goals>
          </execution>
          <execution>
            <?m2e ignore?>
            <id>flatten.clean</id>
            <phase>clean</phase>
            <goals>
              <goal>clean</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Maven-antrun-plugin出现“生命周期配置未涵盖插件执行”错误 - “Plugin execution not covered by lifecycle configuration” error with maven-antrun-plugin 生命周期配置未涵盖Maven插件的执行 - Maven plugin execution not covered by lifecycle configuration 生命周期配置未涵盖插件执行? - Plugin execution not covered by lifecycle configuration? hibernate3-maven-plugin生命周期配置未涵盖插件的执行Eclipse中的错误 - hibernate3-maven-plugin Plugin execution not covered by lifecycle configuration Error in Eclipse Spring 工具套件中的错误“生命周期配置未涵盖插件执行:org.apache.maven.plugins - Error in Spring Tool Suite "Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins 使用父pom中的pluginManagement在eclipse中生命周期配置错误未涵盖插件执行 - Plugin execution not covered by lifecycle configuration error in eclipse with pluginManagement in parent pom 生命周期配置未涵盖插件执行:org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain - Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-toolchains-plugin:1.1:toolchain 生命周期配置AppEngine未涵盖插件执行 - Plugin execution not covered by lifecycle configuration AppEngine Eclipse android Maven:生命周期配置未涵盖插件执行(执行:ndk- build,阶段:编译) - Eclipse android Maven : Plugin execution not covered by lifecycle configuration (execution: ndk- build, phase: compile) 生命周期配置未涵盖插件执行:com.mycila.maven-license-plugin - Plugin execution not covered by lifecycle configuration: com.mycila.maven-license-plugin
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM