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

Konstantin Shvachko commented on HADOOP-15205:
----------------------------------------------

Thanks [~eddyxu] for looking into this. I suggest we update the how-to-release 
page for now, but we should fix it so that "mvn deploy -Psign -DskipTests" 
worked. I am definitely not qualified to deal with maven builds. Do you think 
you can track this, Eddy?

> maven release: missing source attachments for hadoop-mapreduce-client-core
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-15205
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15205
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.7.5, 3.0.0
>            Reporter: Zoltan Haindrich
>            Priority: Major
>
> I wanted to use the source attachment; however it looks like since 2.7.5 that 
> artifact is not present at maven central ; it looks like the last release 
> which had source attachments / javadocs was 2.7.4
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-mapreduce-client-core/2.7.4/
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-mapreduce-client-core/2.7.5/
> this seems to be not limited to mapreduce; as the same change is present for 
> yarn-common as well
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-yarn-common/2.7.4/
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-yarn-common/2.7.5/
> and also hadoop-common
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-common/2.7.4/
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-common/2.7.5/
> http://central.maven.org/maven2/org/apache/hadoop/hadoop-common/3.0.0/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to