[
https://issues.apache.org/jira/browse/MAPREDUCE-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082931#comment-13082931
]
Sharad Agarwal commented on MAPREDUCE-2600:
-------------------------------------------
Thinking more on it. I am inclined to keeping the modules separate as it is
currently, instead of combining the source tree.
I am counting the no of modules to be 10-12. So the source tree should not be
59 or am I missing something.
The separate modules do help identify the boundaries more clearly and help in
*enforcing* those. Separation just based on java packages is loose. I know this
based on the *unnecessary* pain I went thru when I was working on the project
split 2 years ago. In future, refactoring code or doing things like rewriting
NM in C++ will be least intrusive with the current module structure.
If no of jars is the problem, can we just merge the jars at build time the way
we want. Using maven shade plugin or some such ?
> MR-279: simplify the jars
> --------------------------
>
> Key: MAPREDUCE-2600
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2600
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Owen O'Malley
> Assignee: Luke Lu
>
> Currently the MR-279 mapreduce project generates 59 jars from 59 source
> roots, which can be dramatically simplified.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
