[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-6671:
---------------------------------------
Attachment: HADOOP-6671b.patch
Todd,
Thanks for the fast response and detailed review.
I've taken care of all your comments except the one regarding the tools.jar
(still trying to figure out, the Ant <javah> is not finding tools.jar (for some
reason JRE is being used, thus my current hack is still needed).
The following maven options can be used to alter the build/tests:
* -DskipTests
* -DskipDocs
* -DcompileNative
* -Dtest=<TESTCLASS>
> To use maven for hadoop common builds
> -------------------------------------
>
> Key: HADOOP-6671
> URL: https://issues.apache.org/jira/browse/HADOOP-6671
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.22.0
> Reporter: Giridharan Kesavan
> Attachments: HADOOP-6671.patch, HADOOP-6671b.patch, build.png,
> hadoop-commons-maven.patch, mvn-layout.sh, mvn-layout.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
