[
https://issues.apache.org/jira/browse/HDDS-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776001#comment-16776001
]
Hudson commented on HDDS-1165:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16039 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16039/])
HDDS-1165. Document generation in maven should be configured on (bharat: rev
1b87668a3b3ad0bfd6b098037c92a8fd3a8b98f2)
* (edit) hadoop-hdds/docs/pom.xml
> Document generation in maven should be configured on execution 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: Anu Engineer
> Priority: Major
> Fix For: 0.4.0
>
> Attachments: HDDS-1165.001.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
