[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070028#comment-13070028
]
Eric Yang commented on HADOOP-6671:
-----------------------------------
The build structure is coming along nicely. The tarball structure is based on
structure prior to HADOOP-6255. Could we change the file system layout to the
new structure?
The brief layout of the files structure should look like:
{noformat}
$PREFIX/bin/hadoop
$PREFIX/sbin/hadoop-daemon*.sh
/[start|stop]-*.sh
/hadoop-setup*.sh
/hadoop-create-user.sh
$PREFIX/libexec/hadoop-config.sh
$PREFIX/etc/hadoop/*.xml
$PREFIX/lib/*.[so|dylib]
$PREFIX/share/hadoop/common/hadoop*.jar
$PREFIX/share/hadoop/common/lib/*.jar
$PREFIX/share/doc/hadoop/common/*.txt
{noformat}
In addition, could we have package assembly in package phase? Hence, we could
have pre integration test phase to deploy a real cluster, and integration test
phase to run multi-node tests. Verify phase should be used to verify
integration test phase result, and generate clover reports.
Shouldn't tar profile use property ${project.artifactId} for the descriptorRef
for downstream module to reuse this profile? It would be cleaner if
hadoop-assemblies, and hadoop-annotation are part of hadoop-project. The same
applies to src and tar profiles, hence the submodules can reuse the same
profile code.
dev directory could use a better name, like patch-build. It may be alarming
for old school sys admin to see dev filename here. It would be really great if
you could forward porting the rpm/deb packaging target to maven profiles and
invoke maven-ant-plugin. Thanks
> 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-AA.patch, HADOOP-6671-AB.patch,
> 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-AA.sh, mvn-layout-AB.sh,
> 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
