[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852423#action_12852423
]
Steve Loughran commented on HADOOP-6671:
----------------------------------------
I've had bad experiences with M2 in the past; these colour my opinions. I don't
know how much maven2 has improved since then.
What I do have to deal with on a regular basis, even today, is people who write
POM files who get the dependencies correct for their own build and test, but
which screw up everyone else downstream. Recent logging JARs are an example.
Accordingly, I view a POM file as an artifact for downstream users that you
have to get right, not just some internal thing, as we can do today with ivy
and ant files.
This means saying "we should move to maven to eliminate having ivy.xml and POM
files" isn't a good enough reason for me. If it improves testing, build
times,-even to reduce ivy and ant xml maintenance costs, then yes , but not
just "because you can".
> 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.
