Maven 실행자가 자식에 추가됩니다.

Question

maven enforcer 플러그인을 사용하고 있습니다. 부모님과 자식이 pom.xml이라면, exclusions 및 inclusions 태그의 요소가 덮어 쓰기보다는 추가됩니다. 나는 이것을 위해 combine.children="append"을 사용하려고 시도했지만 작동하지만 여분의 configuration 태그로 끝납니다. combine.children을 잘못 사용하고 있으며 추가로 configuration 태그를 사용하지 않으려면 어떻게해야합니까? 부모 pom.xml에서

: 아래의 예를 참조

<project> 
    [...] 
    <build> 
    <plugins> 
     <plugin> 
     <groupId>org.apache.maven.plugins</groupId> 
     <artifactId>maven-enforcer-plugin</artifactId> 
     <version>1.4.1</version> 
     <executions> 
      <execution> 
      <id>enforce-banned-dependencies</id> 
      <goals> 
       <goal>enforce</goal> 
      </goals> 
      <configuration> 
       <rules> 
       <bannedDependencies> 
        <excludes> 
        <exclude>org.apache.maven</exclude> 
        <exclude>org.apache.maven:badArtifact</exclude> 
        <exclude>*:badArtifact</exclude> 
        </excludes> 
        <includes> 
        <!--only 1.0 of badArtifact is allowed--> 
        <include>org.apache.maven:badArtifact:1.0</include> 
        </includes> 
       </bannedDependencies> 
       </rules> 
       <fail>true</fail> 
      </configuration> 
      </execution> 
     </executions> 
     </plugin> 
    </plugins> 
    </build> 
    [...] 
</project> 

을 아이 pom.xml에서 :

<project> 
    [...] 
    <build> 
    <plugins> 
     <plugin> 
     <groupId>org.apache.maven.plugins</groupId> 
     <artifactId>maven-enforcer-plugin</artifactId> 
     <configuration> 
      <rules> 
      <bannedDependencies> 
       <includes combine.children="append"> 
       <include>org.apache.maven:otherArtifact:2.0</include> 
       </includes> 
      </bannedDependencies> 
      </rules> 
     </configuration> 
     </plugin> 
    </plugins> 
    </build> 
    [...] 
</project> 

기대 효과 POM :

<project> 
    [...] 
    <build> 
    <plugins> 
     <plugin> 
     <groupId>org.apache.maven.plugins</groupId> 
     <artifactId>maven-enforcer-plugin</artifactId> 
     <version>1.4.1</version> 
     <executions> 
      <execution> 
      <id>enforce-banned-dependencies</id> 
      <goals> 
       <goal>enforce</goal> 
      </goals> 
      <configuration> 
       <rules> 
       <bannedDependencies> 
        <excludes> 
        <exclude>org.apache.maven</exclude> 
        <exclude>org.apache.maven:badArtifact</exclude> 
        <exclude>*:badArtifact</exclude> 
        </excludes> 
        <includes> 
        <!--only 1.0 of badArtifact is allowed--> 
        <include>org.apache.maven:badArtifact:1.0</include> 
        <include>org.apache.maven:otherArtifact:2.0</include> 
        </includes> 
       </bannedDependencies> 
       </rules> 
       <fail>true</fail> 
      </configuration> 
      </execution> 
     </executions> 
     </plugin> 
    </plugins> 
    </build> 
    [...] 
</project> 

실제 효과 POM :

<project> 
    [...] 
    <build> 
    <plugins> 
     <plugin> 
     <groupId>org.apache.maven.plugins</groupId> 
     <artifactId>maven-enforcer-plugin</artifactId> 
     <version>1.4.1</version> 
     <executions> 
      <execution> 
      <id>enforce-banned-dependencies</id> 
      <goals> 
       <goal>enforce</goal> 
      </goals> 
      <configuration> 
       <rules> 
       <bannedDependencies> 
        <excludes> 
        <exclude>org.apache.maven</exclude> 
        <exclude>org.apache.maven:badArtifact</exclude> 
        <exclude>*:badArtifact</exclude> 
        </excludes> 
        <includes combine.children="append> 
        <!--only 1.0 of badArtifact is allowed--> 
        <include>org.apache.maven:badArtifact:1.0</include> 
        <include>org.apache.maven:otherArtifact:2.0</include> 
        </includes> 
       </bannedDependencies> 
       </rules> 
       <fail>true</fail> 
      </configuration> 
      </execution> 
     </executions> 
     <configuration> 
      <rules> 
      <bannedDependencies> 
       <includes combine.children="append"> 
       <include>org.apache.maven:otherArtifact:2.0</include> 
       </includes> 
      </bannedDependencies> 
      </rules> 
     </configuration> 
     </plugin> 
    </plugins> 
    </build> 
    [...] 
</project> 

Answer 1

당신은 정말 당신이 다음 자녀에 있어야한다 예상되는 합병 구성은 다음 모듈 얻고 싶다면 :

(재 지정을 지적하기 위해 같은 실행 id 값을 재사용입니다

<plugin> 
    <groupId>org.apache.maven.plugins</groupId> 
    <artifactId>maven-enforcer-plugin</artifactId> 
    <executions> 
     <execution> 
      <id>enforce-banned-dependencies</id> 
      <configuration> 
       <rules> 
        <bannedDependencies> 
         <includes> 
          <include>org.apache.maven:badArtifact:2.0</include> 
         </includes> 
        </bannedDependencies> 
       </rules> 
       <fail>true</fail> 
      </configuration> 
     </execution> 
    </executions> 
</plugin> 

/병합) 추가 구성으로 동일한 실행.

그런 다음 병합 효과 치어는 다음과 같은 것입니다 :

<plugin> 
    <artifactId>maven-enforcer-plugin</artifactId> 
    <version>1.4.1</version> 
    <executions> 
     <execution> 
      <id>enforce-banned-dependencies</id> 
      <goals> 
       <goal>enforce</goal> 
      </goals> 
      <configuration> 
       <rules> 
        <bannedDependencies> 
         <includes combine.children="append"> 
          <include>org.apache.maven:badArtifact:1.0</include> 
          <include>org.apache.maven:badArtifact:2.0</include> 
         </includes> 
         <excludes> 
          <exclude>org.apache.maven</exclude> 
          <exclude>org.apache.maven:badArtifact</exclude> 
          <exclude>*:badArtifact</exclude> 
         </excludes> 
        </bannedDependencies> 
       </rules> 
       <fail>true</fail> 
      </configuration> 
     </execution> 
    </executions> 
</plugin> 

는 따라서, 필요가 그것을 사용하지 않으려면 : 기본 병합 동작은 사용자의 요구에 맞게됩니다. 이러한 특성은 그들이에 선언 된 구성 요소에 적용하고, 중첩 된 요소로 전파되지 않도록 official documentation

주에서 combine.* 속성의 사용에 대한

---

한 가지 중요한 참고. 즉, 하위 POM의 항목 요소 콘텐츠가 텍스트가 아닌 복잡한 구조 인 경우 하위 요소 자체에 특성이 표시되어 있지 않으면 하위 요소가 기본 병합 전략의 적용을받습니다.