[
https://issues.apache.org/jira/browse/HADOOP-12361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737471#comment-14737471
]
Allen Wittenauer commented on HADOOP-12361:
-------------------------------------------
It occurred to me this morning that if we re-arrange the source tree now,
there's a lot of potential fallout in how we do our own testing or how Hadoop
does testing. Random thoughts:
* we can't set up our own precommit because issues still come from HADOOP
* merging our branch into hadoop trunk seems like the wrong direction and with
the proposal here, wildly incompatible
* we could switch hadoop-common to use yetus branch to run test-patch, then
point it at a different dir where the hadoop trunk is checked out. yetus
should switch back to our branch based upon the branch detection logic. so that
should work...
* ... but using make for yetus instead of maven means we can't use the hadoop
personality, so how does test-patch know which build system to use for which
type of patch? It also doesn't know how to do that mid-run unless we play some
games with re-exec. (which also seems like a bad idea)
> reorganize repo layout for break from Hadoop code base
> ------------------------------------------------------
>
> Key: HADOOP-12361
> URL: https://issues.apache.org/jira/browse/HADOOP-12361
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: yetus
> Affects Versions: HADOOP-12111
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Attachments: HADOOP-12361.HADOOP-12111.1.sh
>
>
> Reorganize current top level repo to include our starting modules (and only
> those modules), so that it's easier to start bringing in new contributors:
> * shelldoc
> * releasedocmaker
> * interface audience
> * test-patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
