[ 
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alejandro Abdelnur updated HADOOP-6671:
---------------------------------------

    Attachment: HADOOP-6671-h.patch

Wiring Clover.

The following property in the pom.xml may have to set to the correct value in 
the Jenkins servers:
    <cloverLicenseLocation>${user.home}/.clover.license</cloverLicenseLocation>



Build commands avail:

* Clean                     : mvn clean
* Compile                   : mvn compile
* Run tests                 : mvn test
* Create JAR                : mvn package
* Run findbugs              : mvn package -DrunFindbugs
* Run checkstyle            : mvn checkstyle:checkstyle
* TAR wo/docs & wo/source   : mvn package -DmakeTar
* TAR w/docs & w/source     : mvn package -DmakeTar -DgenerateDocs 
-DincludeSource
* TAR w/source only         : mvn assembly:single -Dsource 
* Install in local M2 cache : mvn install
* Deploy to Maven repo      : mvn deploy
* Run clover                : mvn test -DrunClover



> 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
>            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.patch, HADOOP-6671b.patch, 
> HADOOP-6671c.patch, HADOOP-6671d.patch, build.png, 
> hadoop-commons-maven.patch, mvn-layout-e.sh, mvn-layout-f.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

        

Reply via email to