You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrql.apache.org by "Lee moon soo (JIRA)" <ji...@apache.org> on 2014/03/12 05:26:44 UTC
[jira] [Created] (MRQL-32) Refactoring directory structure
Lee moon soo created MRQL-32:
--------------------------------
Summary: Refactoring directory structure
Key: MRQL-32
URL: https://issues.apache.org/jira/browse/MRQL-32
Project: MRQL
Issue Type: Improvement
Reporter: Lee moon soo
Currently all sources stays under /src.
src/main/java/gen
src/main/java/core
src/main/java/BSP
src/main/java/MapReduce
src/main/java/spark
I think it's better to move into each submodule with package named directory tree. like
Gen/src/main/java/org/apache/mrql/gen
core/src/main/java/org/apache/mrql
BSP/src/main/java/org/apache/mrql
MapReduce/src/main/java/org/apache/mrql
Spark/src/main/java/org/apache/mrql
This directory structure gives some advantages
1. More common way.
Most maven projects which has submodule keeps submodule's sources under submodule directory. not in parent directory.
Changing directory structure to more common way will make more developer comfortable.
2. IDE compatible (Eclipse)
mvn eclipse:eclipse generated project file makes src path error.
Changing directory structure will help generating correct eclipse project file.
So developers can benefit from IDE.
--
This message was sent by Atlassian JIRA
(v6.2#6252)