[ 
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034212#comment-13034212
 ] 

Alejandro Abdelnur commented on HADOOP-6671:
--------------------------------------------

Glad to see people are interested in this.

Luke, thanks for the Eclipse info (I don't use Eclipse. I use IntelliJ, 
IntelliJ integrates nicely with Maven, you just open the POM as a project and 
you are  done).

JUnit execution should work fine if you first compile the testcases from Maven 
(running 'mvn test -DskipTests'), I do that trick for IntelliJ. And, if I'm not 
mistaken you should be able to configure the IDE to this automatically (or an 
IDE click).



> 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: build.png, hadoop-commons-maven.patch, 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

Reply via email to