[
https://issues.apache.org/jira/browse/HADOOP-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731884#action_12731884
]
Giridharan Kesavan commented on HADOOP-5107:
--------------------------------------------
steps:
To publish common's jar's to the local repository : ie :
/home/<username>/ivyrepo
cd common-trunk
apply common-trunk.patch
ant ivy-publish-local
this would publish hadoop-core and hadoop-core-test jar to the local filesystem
based repository.
cd hdfs-trunk
apply hdfs-trunk.patch
ant ivy-publish-local -Dresolver=local
this would publish hdfs jars to the local filesystem based repository
-Dresolver=local option tells ivy to resolve the common jars from the local
filesystem based repository
cd mapreduce-trunk
apply mapreduce-trunk.patch
ant ivy-publish-local -Dresolver=local
this would publish mapred jars to the local filesystem based repository
-Dresolver=local option tells ivy to resolve the common and hdfs jars from the
local filesystem based repository
this patch also has a ssh based resolver that publishes artifacts to the people
server's home folder but that requires authentication.
> 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.patch, hdfs-trunk.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.
