Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of stan.ieugen@gmail.com
 designates 209.85.214.41 as permitted sender)
Received-SPF: pass (google.com: domain of stan.ieugen@gmail.com designates
 10.204.174.206 as permitted sender) client-ip=10.204.174.206;
Message-ID: <4F55DAC9.4050809@gmail.com>
Date: Tue, 06 Mar 2012 11:37:13 +0200
From: Ioan Eugen Stan <stan.ieugen@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120104 Icedove/8.0
MIME-Version: 1.0
To: dev@hbase.apache.org
Subject: Re: hbase-0.92.0 up in maven repository
References: 
 <CADcMMgEYez2Jkup8X=D_eqdJTY+RGwOvWx5W6v7NoNzuQNW1iA@mail.gmail.com>
 <CAAva-WcMvmCaeoQ5GeiU7BBLUBH1eSZDbdsrVb87moenWYYDiw@mail.gmail.com>
 <CADcMMgHxEV-go6UeXSfekbdtwYxNho98nQ9O19_LUty=kpoBtA@mail.gmail.com>
 <CAAva-WfTZV8qHv6k5BCrmdVWv12gKVKeUmAOEMKt-fw_KHk4UA@mail.gmail.com>
 <CADcMMgGN6cJHaZfO2fjwb6HVs1S=k9XZer=v8MRiUNXCYtMvXg@mail.gmail.com>
 <CAAva-Wci-xOQF37432ntn3gwXuMSapcwLB=yj3-O7=SVzD=Gjg@mail.gmail.com>
 <CADcMMgFZiePfqPvD1qx5JGzjPF=pOiZhKZ=-Q9ECCx5nh6dzKQ@mail.gmail.com>
 <CAAva-WfAesAiOd-J-e0QZGsHRM35NM83CRfkBn4=5NbW8gtoTw@mail.gmail.com>
 <CADcMMgG1_D_s+x7r7amvzu_cL+4chXoYnZYj4kBByhSw2tq1qw@mail.gmail.com>
In-Reply-To: 
 <CADcMMgG1_D_s+x7r7amvzu_cL+4chXoYnZYj4kBByhSw2tq1qw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Pe 06.03.2012 08:51, Stack a scris:
> On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar<arvind@cloudera.com>  wrote:
>> On Mon, Mar 5, 2012 at 2:40 PM, Stack<stack@duboce.net>  wrote:
>>
>>> On Mon, Mar 5, 2012 at 2:29 PM, Arvind Prabhakar<arvind@cloudera.com>
>>> wrote:
>>>> If this succeeds, you would have staged the tests artifacts successfully.
>>>> Then you can close and release from the staging repository.
>>>>
>>>
>>> Are you thinking the above will succeed though there is already a
>>> 0.92.0 release?  Are you expecting that this deploy will be merged w/
>>> what is already released?
>>>
>>
>> Yes - I think so, although I have not tried it myself before. That said, If
>> you absolutely do not want to take any chances, then you could stage both
>> the main artifact as well as the test artifact before closing the staging
>> repository. In the worst case it will be an overwrite of existing bits with
>> the same binaries as before.
>>
>
> Let me give it a go Arvind.  Will report back.
> St.Ack

I believe you can generate the test jar with:

mvn jar:test-jar [1].

And then deploy how Arvin mentioned. More details here [2], Section 7b: 
Stage Existing Artifacts.


Regards,

[1] http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html
[2] 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
-- 
Ioan Eugen Stan
http://ieugen.blogspot.com