[
https://issues.apache.org/jira/browse/MAPREDUCE-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083202#comment-13083202
]
Owen O'Malley commented on MAPREDUCE-2600:
------------------------------------------
It is a big issue for downstream users. Projects that use Hadoop already pick
up a lot of jars and increasing the set when all of the versions are the same
is a problem. We'll also have users using different versions of the jars, which
won't be useful.
Having a source structure that requires an IDE to use isn't making the code
easy for people to browse, use and modify. It will also become a maintenance
problem as the dependency graph between the components change.
Yes, you can munge the results together into a single jar as part of the build,
but I don't see how it makes development easier or faster to have lots of
little directories.
That said, I don't have cycles to do the work right now. If no one else does
either, we can postpone the debate.
> 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
