[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067194#comment-13067194
]
Alejandro Abdelnur commented on HADOOP-6671:
--------------------------------------------
@Tom,
Thanks.
* On naming. I'd prefer keeping the module names and the artifact names the
same because IDE show the artifact name. When jumping from IDE to command line
and viceversa it will be easier to find your way around.
* On the cross projects build for HDFS and MapReduce. Is possible to commit
that patch independent of this one? Or we'll break Ant builds? If the former,
we should open an HDFS and MR JIRA and do it there. If the later, we should add
your patch to the main HADOOP-6671.
* On running Hadoop from tarball. Last time I'v tried to do that from committed
trunk I've failed miserably. All startup script were pointing to funny places.
* On updating HowToContribute, agree. I've been keeping tabs on BUILDING.txt
file, once this patch is committed we can use it to update the wiki.
How about the following names for the Module/Directory structure?
{code}
trunk/pom.xml
|
|-- hadoop-annotations/pom.xml (renaming doclets)
|
|-- hadoop-project/pom.xml
|
|-- common/pom.xml
| |
| |-- hadoop-common/pom.xml
| |
| |-- hadoop-common-docs/pom.xml
| |
| |-- hadoop-common-tar/pom.xml
|
|-- hdfs
|
|-- mapreduce
{code}
We'd have also a {{hadoop-common-rpm}} and {{hadoop-common-deb}}.
Then hdfs/mapreduce would have a similar structure.
And there would be a {{hadoop-contribs}} with a submodule for contrib project
(which could have sub-sub-modules).
> To use maven for hadoop common builds
> -------------------------------------
>
> Key: HADOOP-6671
> URL: https://issues.apache.org/jira/browse/HADOOP-6671
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
> Affects Versions: 0.22.0
> Reporter: Giridharan Kesavan
> Assignee: Alejandro Abdelnur
> Attachments: HADOOP-6671-cross-project-HDFS.patch,
> HADOOP-6671-e.patch, HADOOP-6671-f.patch, HADOOP-6671-g.patch,
> HADOOP-6671-h.patch, HADOOP-6671-i.patch, HADOOP-6671-j.patch,
> HADOOP-6671-k.sh, HADOOP-6671-l.patch, HADOOP-6671-m.patch,
> HADOOP-6671-n.patch, HADOOP-6671-o.patch, HADOOP-6671-p.patch,
> HADOOP-6671-q.patch, HADOOP-6671.patch, HADOOP-6671b.patch,
> HADOOP-6671c.patch, HADOOP-6671d.patch, build.png, common-mvn-layout-i.sh,
> hadoop-commons-maven.patch, mvn-layout-e.sh, mvn-layout-f.sh,
> mvn-layout-k.sh, mvn-layout-l.sh, mvn-layout-m.sh, mvn-layout-n.sh,
> mvn-layout-o.sh, mvn-layout-p.sh, mvn-layout-q.sh, mvn-layout.sh,
> mvn-layout.sh, mvn-layout2.sh, mvn-layout2.sh
>
>
> We are now able to publish hadoop artifacts to the maven repo successfully [
> Hadoop-6382]
> Drawbacks with the current approach:
> * Use ivy for dependency management with ivy.xml
> * Use maven-ant-task for artifact publishing to the maven repository
> * pom files are not generated dynamically
> To address this I propose we use maven to build hadoop-common, which would
> help us to manage dependencies, publish artifacts and have one single xml
> file(POM) for dependency management and artifact publishing.
> I would like to have a branch created to work on mavenizing hadoop common.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
