[
https://issues.apache.org/jira/browse/HADOOP-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Lu updated HADOOP-7019:
----------------------------
Attachment: hadoop-7019-trunk-v2.patch
v2 patch only moves si artifact out of mvn-install, as fi test issue has a
workaround (not proper because run-test-core is not supposed to be a user
facing target.)
bq. I'll try to explain it once more:
You know I meant test and test-patch as one process. Also test-patch does also
exercise the fi compilation.
bq. Sorry, where the multiplier comes from? Does it indicates the number of
subprojects?
Simple math: 71 / 20 = 3.55
bq. ant run-test-core... will produce desired result.
run-* targets are not user facing, i.e., they're implementation details.
> Refactor build targets to enable faster cross project dev cycles.
> -----------------------------------------------------------------
>
> Key: HADOOP-7019
> URL: https://issues.apache.org/jira/browse/HADOOP-7019
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Owen O'Malley
> Assignee: Luke Lu
> Fix For: 0.22.0
>
> Attachments: hadoop-7019-trunk-v1.patch, hadoop-7019-trunk-v2.patch
>
>
> The current build always generates fault injection artifacts and pushes them
> to Maven. Most developers have no need for these artifacts and no users need
> them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
