[
https://issues.apache.org/jira/browse/HDDS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877246#comment-16877246
]
Eric Yang commented on HDDS-1661:
---------------------------------
I think to address this issue to help reduce friction for Ozone developer
adoption. GA might be too late because bad code hygiene will steer away more
potential developers from now until GA. I understand the argument for keeping
HDDS a potential integration point with HDFS. I also accept the reasoning that
keeping HDFS stable without integrating with HDDS. Moving a maven module
should not be difficult, otherwise it is bad code hygiene. If there is a
stronger commitment from HDFS to integration with HDDS later, then promote the
package back would make sense. Having HDDS out of place, it hinders new
developers ability to build the system with mvn clean package and it brain wash
current developers with odd behaviors.
> 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]
