hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2600) MR-279: simplify the jars
Date Thu, 11 Aug 2011 16:55:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083225#comment-13083225

Alejandro Abdelnur commented on MAPREDUCE-2600:

59 JARs for a project seems a bit too much, it seems that JARs are being used instead of Java
packages to separate class.

IMO, a more logical set of JARs is along the lines of Owen described when opening the JIRA:
api, client, server, utils

Even if IDEs can handle several source roots, 59 becomes cumbersome. Plus, from Maven side,
that means the reactor will do much more work to resolve module dependency, thus slowing down
the build.

Finally, I advice against merging JARs into one, this complicates significantly troubleshooting.

> 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


View raw message