[
https://issues.apache.org/jira/browse/MRQL-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931753#comment-13931753
]
Leonidas Fegaras commented on MRQL-32:
--------------------------------------
Lee moon,
Thank you for the patch. I applied your patch and MRQL compiles and runs as
before. I don't use Eclipse. I only use a text editor. In order to approve this
patch (needs two votes from PPC), please tell us how to import the project on
Eclipse after you build it using 'mvn eclipse:eclipse' and how you rebuild MRQL
from inside Eclipse. These directions will also go to the developer's guide.
Thank you
> Refactoring directory structure for Eclipse
> -------------------------------------------
>
> Key: MRQL-32
> URL: https://issues.apache.org/jira/browse/MRQL-32
> Project: MRQL
> Issue Type: Improvement
> Reporter: Lee moon soo
> Assignee: Leonidas Fegaras
> Priority: Critical
> Attachments: MRQL-32.patch
>
>
> 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)
