[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-6671:
---------------------------------------
Attachment: mvn-layout2.sh
HADOOP-6671d.patch
Integrated checkstyle and findbugs, added option to skipDocs.
Only thing missing is JDiff integration (which it seems a dead project and the
Maven plugin does not seem to work properly).
Is JDIFF required? Any other alternative?
Maven goals:
* clean
* compile (-DcompileNative)
* test (-DcompileNative, -Dtest=<TESTCLASS>, -DskipTests)
* package (-DcompileNative, -DskipDocs, -DskipTests | -Dtest=<TESTCLASS>)
* checkstyle:checkstyle
* findbugs:findbugs
> 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,
> HADOOP-6671c.patch, HADOOP-6671d.patch, build.png,
> hadoop-commons-maven.patch, mvn-layout.sh, mvn-layout.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
