I was able to publish HDFS and Common, but couldn't publish MR/YARN due to:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy
(default-deploy) on project hadoop-yarn-api: Deployment failed:
repository element was not specified in the POM inside
distributionManagement element or in
-DaltDeploymentRepository=id::layout::url parameter -> [Help 1]

I think this is MAPREDUCE-3003. Will wait on Tom or Alejandro to fix that.

-Todd

On Fri, Oct 14, 2011 at 12:57 PM, Arun C Murthy <a...@hortonworks.com> wrote:
> +1, thanks Todd.
>
> On Oct 14, 2011, at 12:53 PM, Todd Lipcon wrote:
>
>> On Fri, Oct 14, 2011 at 12:39 PM, giridharan kesavan
>> <gkesa...@hortonworks.com> wrote:
>>> Todd,
>>> I like the idea of setting up commit builds for 23 branch; I can set this
>>> up.
>>
>> OK. Mind if I manually mvn deploy for now? Some HBase work is blocked on it.
>>
>> -Todd
>>
>>>
>>> On 10/14/11 12:23 PM, Todd Lipcon wrote:
>>>>
>>>> Looks like the Hadoop-*-Commit builds for trunk do a mvn deploy, but
>>>> not the 0.23 builds.
>>>>
>>>> It seems we should either (a) add "mvn deploy" to the
>>>> Hadoop-*-0.23-Build targets (which run nightly), or (b) add a
>>>> cross-project "0.23-commit" build which is triggered on any commit to
>>>> 0.23 and does a mvn deploy across all the projects, without running
>>>> any tests.
>>>>
>>>> Any preferences?
>>>>
>>>> On Fri, Oct 14, 2011 at 12:18 PM, Todd Lipcon<t...@cloudera.com>  wrote:
>>>>>
>>>>> It seems that we're not publishing maven snapshots correctly. I'm not
>>>>> entirely sure why, but if you look at:
>>>>>
>>>>> https://repository.apache.org/content/groups/snapshots/org/apache/hadoop/hadoop-common/
>>>>> you'll see the latest snapshots are from 9/14 or so.
>>>>>
>>>>> Anyone have any idea what's going on here?
>>>>>
>>>>> -Todd
>>>>> --
>>>>> Todd Lipcon
>>>>> Software Engineer, Cloudera
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> -Giri
>>>
>>>
>>
>>
>>
>> --
>> Todd Lipcon
>> Software Engineer, Cloudera
>
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Reply via email to