Return-Path: X-Original-To: apmail-repository-archive@www.apache.org Delivered-To: apmail-repository-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD0D9904C for ; Tue, 31 Jan 2012 21:38:47 +0000 (UTC) Received: (qmail 74624 invoked by uid 500); 31 Jan 2012 21:38:47 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 74479 invoked by uid 500); 31 Jan 2012 21:38:46 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 74459 invoked by uid 99); 31 Jan 2012 21:38:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 21:38:46 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of msa@schor.com designates 64.5.52.12 as permitted sender) Received: from [64.5.52.12] (HELO gateway09.websitewelcome.com) (64.5.52.12) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 21:38:37 +0000 Received: by gateway09.websitewelcome.com (Postfix, from userid 507) id B6D21C5DDD1DE; Tue, 31 Jan 2012 15:38:15 -0600 (CST) Received: from gator74.hostgator.com (gator74.hostgator.com [184.173.199.208]) by gateway09.websitewelcome.com (Postfix) with ESMTP id A8620C5DDD1BA for ; Tue, 31 Jan 2012 15:38:15 -0600 (CST) Received: from [129.34.20.19] (port=54847 helo=[9.2.34.182]) by gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RsLP5-0007Tl-HA for repository@apache.org; Tue, 31 Jan 2012 15:38:15 -0600 Message-ID: <4F285F41.1060605@schor.com> Date: Tue, 31 Jan 2012 16:38:09 -0500 From: Marshall Schor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: repository@apache.org Subject: Re: adding some artifacts to our last release in Maven central References: <4F270A5B.7030705@schor.com> <4F27F491.7040102@schor.com> <4F285A74.3080908@schor.com> In-Reply-To: <4F285A74.3080908@schor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator74.hostgator.com X-AntiAbuse: Original Domain - apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schor.com X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: yktgi01e0-s5.watson.ibm.com ([9.2.34.182]) [129.34.20.19]:54847 X-Source-Auth: msa+schor.com X-Email-Count: 2 X-Source-Cap: bWlzY2hvcjttaXNjaG9yO2dhdG9yNzQuaG9zdGdhdG9yLmNvbQ== X-Virus-Checked: Checked by ClamAV on apache.org I see Nexus Jira https://issues.sonatype.org/browse/NEXUS-4759 which was closed just last week, about a similar kind of hang. Do we need to update our Nexus to pick up this change? -Marshall On 1/31/2012 4:17 PM, Marshall Schor wrote: > I found that by "logging in" to repository.apache.org, I got the menu pick > "Staging Upload", which would seem to do exactly what I want. > > But -- it just hangs when I try to upload the artifacts. I reduced it to > just uploading the POM for the project (which I think should pass any tests > the upload might perform - because it's the one that was used to build / > release the release). > > It does manage to create the staging repository, but doesn't upload anything. > I've tried both Chrome and Firefox browsers (after reading that there was an > issue with Chrome). > > Any suggestions? Should I file a Jira (I saw several other Jiras about > uploads hanging, but with no clear resolution). > > -Marshall Schor > > On 1/31/2012 9:02 AM, Marshall Schor wrote: >> We have recently discovered that our last UIMA SDK 2.4.0 release seems to be >> missing a couple of artifacts on Maven central. I have the artifacts from the >> release build still sitting in my local maven (.m2) repository, and would >> like to get them up to Maven central. Is there a way to do that? I thought I >> could maybe (1) create a new staging repository instance on >> repository.apache.org - similar to what happens when I do a release >> candidate, but where I could somehow "upload" the artifacts from my .m2 repo, >> and then "push the release button". But I don't see a way to do that in the >> repository.apache.org instance of Nexus. >> >> Thanks. -Marshall >> >