You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/02/22 22:22:00 UTC

[jira] [Created] (HDDS-1165) Document generation in maven should be configured on execition level

Elek, Marton created HDDS-1165:
----------------------------------

             Summary: Document generation in maven should be configured on execition level 
                 Key: HDDS-1165
                 URL: https://issues.apache.org/jira/browse/HDDS-1165
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
            Reporter: Elek, Marton
            Assignee: Elek, Marton


Documentation of Ozone/Hdds project is generated from maven with the help of maven exec plugin.

There are multiple ways to configure plugins in maven. Plugin can be configured on plugin level:
{code:java}
<plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>exec-maven-plugin</artifactId>
        <version>1.6.0</version>
        <executions>
          <execution>
            <goals>
              <goal>exec</goal>
            </goals>
            <phase>compile</phase>
          </execution>
        </executions>
        <configuration>
          ...
        </configuration>
      </plugin>
{code}
In this case not only the specific execution but all the execution will be configured (even if it's triggered by mvn exec:exec)

Or it can be configured on the execution level:
{code:java}
<plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>exec-maven-plugin</artifactId>
        <version>1.6.0</version>
        <executions>
          <execution>
            <goals>
              <goal>exec</goal>
            </goals>
            <phase>compile</phase>
             <configuration>
             ...
             </configuration>
          </execution>
        </executions>
        
      </plugin>{code}
In this case the configuration is valid only for this specific execution which is bound to a specific phase (compile in this case)

Unfortunately it's configured in the wrong way in hadoop-hdds/docs/pom.xml: the first approach should be replaced with the second with moving the configuration to inside the execution.

Without this change yetus can't detect the dependency order.

How to test:

The easiest way to reproduce the problem is to execute:
{code:java}
mvn  -fae exec:exec -Dexec.executable=pwd -Dexec.args='' -Phdds{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org