You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2015/11/19 15:17:10 UTC
[jira] [Updated] (YETUS-170) hadoop mvninstall should run changed
modules in dependency order
[ https://issues.apache.org/jira/browse/YETUS-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinayakumar B updated YETUS-170:
--------------------------------
Summary: hadoop mvninstall should run changed modules in dependency order (was: hadoop mvninstall should run on parent directories of changed modules)
> 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
>
>
> 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)