[
https://issues.apache.org/jira/browse/HADOOP-6200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744981#action_12744981
]
Steve Loughran commented on HADOOP-6200:
----------------------------------------
Hadoop-hdfs depends on hadoop-mapreduce for testing, hence, a cycle.
Right now I am playing tricks with symlinks to hook up the lib directories, so
what I build in one dir is automatically picked up by the adjacent project -and
documenting what I am doing for the hadoop wiki- but its a bit complex.
options
# flatten : pull out hadoop-hdfs.run-test-hdfs-with-mr bit and move to a
subproject that depends on hadoop-hdfs and hadoop-mapreduce
# boostrap via the central repository. Rather than have copies of artifacts in
the different bits of SVN, stick some alpha releases of everything up onto the
central repository. Then you can use ivy to pull things in, so when I build
hdfs the latest version of common gets picked up, and the latest version of
mapreduce. If I publish locally, I get the version I ask for, but the default
would be to get the last release on the central repo.
I'm coming round in favour of #2, because it helps us debug the publishing
process with, say, a fortnightly alpha release of the artifacts (PMC approval
still needed, incidentally), so that when the time comes to do real beta
releases, the POMs and such like are stable.
> glue together the different projects to make local builds easier
> ----------------------------------------------------------------
>
> Key: HADOOP-6200
> URL: https://issues.apache.org/jira/browse/HADOOP-6200
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Priority: Minor
>
> It's currently fairly tricky to get everything building/up to date in a
> single machine. We can and should improve this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
