hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Smith (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6671) To use maven for hadoop common builds
Date Wed, 07 Apr 2010 03:32:33 GMT

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

Paul Smith commented on HADOOP-6671:
------------------------------------

Lars beat me to the jira comment, so I'll just say "Yeah, what Lars said".

Happy to put my hand up to help, rather than a branch, I'd say a simply script like what was
in HBASE-2099 is simple to work with for a reviewer, it outlines the migration steps needed
rather than some hideous patch to review.

In regards to AllanW's comments on sync'ing things around, that is still possible, rather
than sync'ng the .ivy directory it's just ensuring the ~/.m2/repository directories are in
sync, and then working in Maven's offline mode if that server doesn't have internet connectivity.

Yes, one has to get the POM right, and that does come with experience, so perhaps if Lars
and I can help here to get it off in the right direction that can ease any potential pain.
   IntelliJ and Eclipse Maven support is now 1st-class citizens really, Ivy less so.    For
future modularization, the Maven migration will pay off, splitting out code into nice modular
chunks becomes much less work keeping the build system in sync.

Anyway, happy to help out here too.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message