[
https://issues.apache.org/jira/browse/MAPREDUCE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13105813#comment-13105813
]
Alejandro Abdelnur commented on MAPREDUCE-3003:
-----------------------------------------------
#1 is far from ideal, it is an error prone hack. Besides, this the pros you
mention for this approach are easily doable using the version plugin (as it is
done today for all the non MR modules).
Just to give an example, I was doing 'mvn install' from trunk/ today and the MR
POMs are un-usable. If there is something special to do a correct deployment of
them it is not the maven way and developers will get bitten by it.
A strong -1 on this approach.
#2 is the right way of doing things in Maven, it is easy, straight forward and
any developer familiar with Maven (or learning) will understand what is going
on.
Furthermore, as discussed when we were working on common/hdfs mavenization the
maven version plugin can be used to set versions global for CI purposes. And I
believe this is what is being done for common & hdfs currently (or it is the
plan).
> Publish Yarn and MapReduce artifacts to Maven snapshot repository
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-3003
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3003
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: build
> Reporter: Tom White
> Assignee: Tom White
> Attachments: MAPREDUCE-3003-0.23.patch, MAPREDUCE-3003.patch,
> MAPREDUCE-3003.patch
>
>
> Currently this is failing since no distribution management section is defined
> in the POM.
> https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-trunk-Commit/883/consoleFull
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
