[
https://issues.apache.org/jira/browse/HADOOP-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-7533:
------------------------------
Attachment: HADOOP-7533.patch
This patch:
* Removes hard-coded dependencies on the common project. It now looks for
test-patch.properties (which contains the number of allowed warnings) in
dev-support so each subproject defines its own.
* Changes test-patch.sh so it can run at the project root (hadoop-trunk) or a
subproject module (e.g. hadoop-trunk/hadoop-common).
* Changes smart-patch-apply.sh so it can handle cross-project patches.
I ran the same sequence of commands as Todd in
https://issues.apache.org/jira/browse/HADOOP-7384?focusedCommentId=13048441&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13048441,
with the same results.
In addition I ran the following from the project root
{noformat}
% git diff | PATCH=echo dev-support/smart-apply-patch.sh -
Looks like this is a git patch. Stripping a/ and b/ prefixes
and incrementing PLEVEL
Looks like this is being run at project root
Going to apply patch with: echo -p1
-p1 -E
{noformat}
I also verified that test-patch can be successfully run from the top level and
from hadoop-common.
> Allow test-patch to be run from any subproject directory
> ---------------------------------------------------------
>
> Key: HADOOP-7533
> URL: https://issues.apache.org/jira/browse/HADOOP-7533
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Tom White
> Assignee: Tom White
> Attachments: HADOOP-7533.patch
>
>
> Currently dev-support/test-patch.sh can only be run from the top-level (and
> only for hadoop-common).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
