[ 
https://issues.apache.org/jira/browse/HDDS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878045#comment-16878045
 ] 

Eric Yang edited comment on HDDS-1661 at 7/3/19 6:11 PM:
---------------------------------------------------------

[~anu] When doing a directory moving, the better strategy is to provide a shell 
script that runs git mv command to avoid posting large patch and provide better 
history for the linear-age of the code.  Besides the git mv script, there are 
some shell integration scripts that should be modified because the integration 
script are semi-hard coded relative path to reference hadoop-hdds project.    
If we can avoid generating shell scripts as wrapper on top of maven, it will 
save us a lot of work.  This is the reason that I voiced my concern in 
HDDS-1735 about the shell script wrappers.  If the project continue in current 
direction, it will be hard to move later on.  I hope you would reconsider.


was (Author: eyang):
[~anu] When doing a directory moving, the better strategy is to provide a shell 
script that runs git mv command to avoid posting large patch and provide better 
history for the linear-age of the code.  Besides the git mv script, there are 
some shell integration scripts that should be modified because the integration 
script are semi-hard coded relative path to reference hadoop-hdds project.    
If we can avoid generating shell scripts as wrapper on top of maven, it will 
save us a lot of work.  This is the reason that I voiced by concern in 
HDDS-1735 about the shell script wrappers.  If the project continue in current 
direction, it will be hard to move later on.  I hope you would reconsider.

> Consolidate hadoop-hdds and hadoop-ozone into hadoop-ozone-project
> ------------------------------------------------------------------
>
>                 Key: HDDS-1661
>                 URL: https://issues.apache.org/jira/browse/HDDS-1661
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Eric Yang
>            Priority: Major
>
> Ozone source code is some what fragmented in Hadoop source code.  The current 
> code looks like:
> {code}
> hadoop/pom.ozone.xml
> ├── hadoop-hdds
> └── hadoop-ozone
> {code}
> It is helpful to consolidate the project into high level grouping such as:
> {code}
> hadoop
> └── hadoop-ozone-project/pom.xml
> └── hadoop-ozone-project/hadoop-hdds
> └── hadoop-ozone-project/hadoop-ozone
> {code}
> This allows user to build ozone from hadoop-ozone-project directory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to