[
https://issues.apache.org/jira/browse/HADOOP-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038720#comment-13038720
]
Tom White commented on HADOOP-6671:
-----------------------------------
We currently publish jdiff documentation as a part of a release (e.g.
http://hadoop.apache.org/common/docs/r0.20.2/jdiff/changes.html). There's also
HADOOP-7035 which refines this to publish changes categorized by API stability
and compatibility (there is an example at
http://people.apache.org/~tomwhite/HADOOP-7035/common/).
HADOOP-7035 will include documenting the process for generating jdiff for a
release, so I don't think that we need to get it integrated in Maven as a part
of this issue. (If needed at a later point we could hook it into Maven by
calling out to the script.) Does that sound reasonable?
> 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
