[
https://issues.apache.org/jira/browse/HADOOP-12361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729280#comment-14729280
]
Allen Wittenauer commented on HADOOP-12361:
-------------------------------------------
Any thoughts on where/how to handle unit tests? As soon as the layout gets
settled, I want to start getting some in...
bq. any particular reason? in the case of version-info I think I've convinced
myself that it should go to the Maven project. But we'll like have some other
java artifact at some time in the future. I've been presuming the different
components will be versioned independently, since they aren't directly tied to
each other.
>From what I've seen of the build systems we support, maven is probably the
>best for support Java-based bits.
bq. I've been hoping (and the current proposal presumes) that we'll use the new
git based publishing system (ref blog), which I think will render markdown (or
asciidoc or whatever) for us.
We should verify that.
bq. we you thinking a common docs/ dir would be easier to migrate to whatever
gets decided?
I think per-"project" docs are the way to go, but just worried about having
five files called README.md and what that means for web site generation.
> 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)
