[
https://issues.apache.org/jira/browse/HADOOP-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758649#action_12758649
]
Jothi Padmanabhan commented on HADOOP-5107:
-------------------------------------------
I tested this out. I did
1. Made change to a common file
2. Compiled and published it locally using {noformat} ant mvn-install {noformat}
3. Made some changes to mapreduce source to use the change I did in the common
file
4. Compiled using {noformat} ant -Dresolvers=internal {noformat}
The compilation went through fine.
> split the core, hdfs, and mapred jars from each other and publish them
> independently to the Maven repository
> ------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-5107
> URL: https://issues.apache.org/jira/browse/HADOOP-5107
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.20.0
> Reporter: Owen O'Malley
> Assignee: Giridharan Kesavan
> Attachments: common-trunk-v1.patch, common-trunk-v4.patch,
> common-trunk.patch, hadoop-hdfsd-v4.patch, hdfs-trunk-v1.patch,
> hdfs-trunk-v2.patch, hdfs-trunk.patch, mapred-trunk-v1.patch,
> mapred-trunk-v2.patch, mapred-trunk-v3.patch, mapred-trunk-v4.patch,
> mapreduce-trunk.patch
>
>
> I think to support splitting the projects, we should publish the jars for
> 0.20.0 as independent jars to the Maven repository
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
