[
https://issues.apache.org/jira/browse/YETUS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013800#comment-15013800
]
Yetus QA commented on YETUS-170:
--------------------------------
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at
https://builds.apache.org/job/PreCommit-YETUS-Build/121/console in case of
problems.
> hadoop mvninstall should run changed modules in dependency order
> ----------------------------------------------------------------
>
> Key: YETUS-170
> URL: https://issues.apache.org/jira/browse/YETUS-170
> Project: Yetus
> Issue Type: Bug
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: YETUS-170-01.patch, YETUS-170-02.patch,
> YETUS-170-03.patch, YETUS-170-04.patch, YETUS-170-05.patch, YETUS-170-06.patch
>
>
> https://builds.apache.org/job/PreCommit-HDFS-Build/13397/console
> If the patch contains multiple modules changed, then mvn install is expected
> to run in order of dependency.
> For example, if hadoop-hdfs and hadoop-hdfs-client is changed, then
> hadoop-hdfs-client is expected to run first and then hadoop-hdfs.
> Instead, can run mvn install on parent of both these modules. Same is done
> for 'compile', but not for 'mvninstall'
> This Jira proposes to run mvninstall for hadoop on parent of changed modules
> (union)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
