I managed to release hbase-0.92.0 to the apache maven repository.  It
has the source, doc, and bin jars.  It does not include the test jar.
Will try and fix this for hbase 0.92.1 release.

Its been a bit of a comedy of errors getting this far.  I'll add what
I learned to the reference guide.

Will try to do better next time (Maven 7, Stack 2)

St.Ack
P.S. Thanks to Ulrich for showing me how to skip running tests at each
stage of the release process.

Good news.

Looking forward to the artifacts propagated to
http://repo2.maven.org/maven2/org/apache/hbase/hbase/

On Fri, Mar 2, 2012 at 8:48 AM, Stack <[EMAIL PROTECTED]> wrote:

> I managed to release hbase-0.92.0 to the apache maven repository.  It
> has the source, doc, and bin jars.  It does not include the test jar.
> Will try and fix this for hbase 0.92.1 release.
>
> Its been a bit of a comedy of errors getting this far.  I'll add what
> I learned to the reference guide.
>
> Will try to do better next time (Maven 7, Stack 2)
>
> St.Ack
> P.S. Thanks to Ulrich for showing me how to skip running tests at each
> stage of the release process.
>

Well done!

:-)

On Fri, Mar 2, 2012 at 5:48 PM, Stack <[EMAIL PROTECTED]> wrote:

> I managed to release hbase-0.92.0 to the apache maven repository.  It
> has the source, doc, and bin jars.  It does not include the test jar.
> Will try and fix this for hbase 0.92.1 release.
>
> Its been a bit of a comedy of errors getting this far.  I'll add what
> I learned to the reference guide.
>
> Will try to do better next time (Maven 7, Stack 2)
>
> St.Ack
> P.S. Thanks to Ulrich for showing me how to skip running tests at each
> stage of the release process.
>

Thanks stack. That's great.

On Fri, Mar 2, 2012 at 8:55 AM, N Keywal <[EMAIL PROTECTED]> wrote:

> Well done!
>
> :-)
>
> On Fri, Mar 2, 2012 at 5:48 PM, Stack <[EMAIL PROTECTED]> wrote:
>
> > I managed to release hbase-0.92.0 to the apache maven repository.  It
> > has the source, doc, and bin jars.  It does not include the test jar.
> > Will try and fix this for hbase 0.92.1 release.
> >
> > Its been a bit of a comedy of errors getting this far.  I'll add what
> > I learned to the reference guide.
> >
> > Will try to do better next time (Maven 7, Stack 2)
> >
> > St.Ack
> > P.S. Thanks to Ulrich for showing me how to skip running tests at each
> > stage of the release process.
> >
>

Good on you Stack.

J-D

On Fri, Mar 2, 2012 at 8:48 AM, Stack <[EMAIL PROTECTED]> wrote:
> I managed to release hbase-0.92.0 to the apache maven repository.  It
> has the source, doc, and bin jars.  It does not include the test jar.
> Will try and fix this for hbase 0.92.1 release.
>
> Its been a bit of a comedy of errors getting this far.  I'll add what
> I learned to the reference guide.
>
> Will try to do better next time (Maven 7, Stack 2)
>
> St.Ack
> P.S. Thanks to Ulrich for showing me how to skip running tests at each
> stage of the release process.

Downstream projects will be  very happy. Thanks Stack.

Enis

On Fri, Mar 2, 2012 at 10:55 AM, Jean-Daniel Cryans <[EMAIL PROTECTED]>wrote:

> Good on you Stack.
>
> J-D
>
> On Fri, Mar 2, 2012 at 8:48 AM, Stack <[EMAIL PROTECTED]> wrote:
> > I managed to release hbase-0.92.0 to the apache maven repository.  It
> > has the source, doc, and bin jars.  It does not include the test jar.
> > Will try and fix this for hbase 0.92.1 release.
> >
> > Its been a bit of a comedy of errors getting this far.  I'll add what
> > I learned to the reference guide.
> >
> > Will try to do better next time (Maven 7, Stack 2)
> >
> > St.Ack
> > P.S. Thanks to Ulrich for showing me how to skip running tests at each
> > stage of the release process.
>

On Fri, Mar 2, 2012 at 1:20 PM, Enis Söztutar <[EMAIL PROTECTED]> wrote:
> Downstream projects will be  very happy. Thanks Stack.
>

Need to get tests up there when we do 0.92.1, and security.
St.Ack

Would it be possible to manually deploy the tests-jar for 0.92.0? Sqoop
dependes upon this artifact and is unable to use this release because of
this reason.

Thanks,
Arvind

On Fri, Mar 2, 2012 at 8:48 AM, Stack <[EMAIL PROTECTED]> wrote:

> I managed to release hbase-0.92.0 to the apache maven repository.  It
> has the source, doc, and bin jars.  It does not include the test jar.
> Will try and fix this for hbase 0.92.1 release.
>
> Its been a bit of a comedy of errors getting this far.  I'll add what
> I learned to the reference guide.
>
> Will try to do better next time (Maven 7, Stack 2)
>
> St.Ack
> P.S. Thanks to Ulrich for showing me how to skip running tests at each
> stage of the release process.
>

On Mon, Mar 5, 2012 at 9:08 AM, Arvind Prabhakar <[EMAIL PROTECTED]> wrote:
> Would it be possible to manually deploy the tests-jar for 0.92.0? Sqoop
> dependes upon this artifact and is unable to use this release because of
> this reason.
>

Pardon my bungling.

Does anyone know how to do the above?

St.Ack
P.S. Ioan has volunteered to help me w/ next release to maven
off-list.  Between Ulrich and Ioan, between the two of them, hey
should be able to right my erroneous ways.

On Mon, Mar 5, 2012 at 12:52 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Mon, Mar 5, 2012 at 9:08 AM, Arvind Prabhakar <[EMAIL PROTECTED]>
> wrote:
> > Would it be possible to manually deploy the tests-jar for 0.92.0? Sqoop
> > dependes upon this artifact and is unable to use this release because of
> > this reason.
> >
>
> Pardon my bungling.
>
> Does anyone know how to do the above?
>

We have documented the manual steps for doing this for Sqoop at:

https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release#HowtoRelease-PublishbinaryartifactsinMavenRepository

If you can get to the locally built artifacts (say in your local maven
cache), you can use these instructions to publish them.
>
> St.Ack
> P.S. Ioan has volunteered to help me w/ next release to maven
> off-list.  Between Ulrich and Ioan, between the two of them, hey
> should be able to right my erroneous ways.
>

On Mon, Mar 5, 2012 at 2:10 PM, Arvind Prabhakar <[EMAIL PROTECTED]> wrote:
> We have documented the manual steps for doing this for Sqoop at:
>
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release#HowtoRelease-PublishbinaryartifactsinMavenRepository
>
> If you can get to the locally built artifacts (say in your local maven
> cache), you can use these instructions to publish them.
>

HBase 0.92.0 is beyond what these steps presume, right?  Its actually
released minus the test jar.  The instructions don't seem to have any
help for this particular predicament?
Thanks,
St.Ack

On Mon, Mar 5, 2012 at 2:16 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Mon, Mar 5, 2012 at 2:10 PM, Arvind Prabhakar <[EMAIL PROTECTED]>
> wrote:
> > We have documented the manual steps for doing this for Sqoop at:
> >
> >
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release#HowtoRelease-PublishbinaryartifactsinMavenRepository
> >
> > If you can get to the locally built artifacts (say in your local maven
> > cache), you can use these instructions to publish them.
> >
>
> HBase 0.92.0 is beyond what these steps presume, right?  Its actually
> released minus the test jar.  The instructions don't seem to have any
> help for this particular predicament?
>

Here is one way to do it:

1. Checkout the sources associated with the release somewhere convenient.
2. Do a "mvn clean install" on these sources. This will hopefully
produce hbase-0.92.0-tests.jar under the target directory.
3. Make sure you have setup your settings.xml as described in the Sqoop
wiki page. Then run the following command using this artifact:
$ mvn gpg:sign-and-deploy-file -Dfile=./hbase-0.92.0-tests.jar
-DrepositoryId=apache.staging.https
-Durl=https://repository.apache.org/service/local/staging/deploy/maven2/
-Dgpg.keyname=<your-gpg-keyname> -Dclassifier=tests

If this succeeds, you would have staged the tests artifacts successfully.
Then you can close and release from the staging repository.

Thanks,
Arvind

> Thanks,
> St.Ack
>

On Mon, Mar 5, 2012 at 2:29 PM, Arvind Prabhakar <[EMAIL PROTECTED]> 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?

Thanks,
St.Ack

On Mon, Mar 5, 2012 at 2:40 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Mon, Mar 5, 2012 at 2:29 PM, Arvind Prabhakar <[EMAIL PROTECTED]>
> 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.

Thanks,
Arvind
>
> Thanks,
> St.Ack
>

On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 5, 2012 at 2:40 PM, Stack <[EMAIL PROTECTED]> wrote:
>
>> On Mon, Mar 5, 2012 at 2:29 PM, Arvind Prabhakar <[EMAIL PROTECTED]>
>> 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

Pe 06.03.2012 08:51, Stack a scris:
> On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar<[EMAIL PROTECTED]>  wrote:
>> On Mon, Mar 5, 2012 at 2:40 PM, Stack<[EMAIL PROTECTED]>  wrote:
>>
>>> On Mon, Mar 5, 2012 at 2:29 PM, Arvind Prabhakar<[EMAIL PROTECTED]>
>>> 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

On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]> wrote:
> 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.
>

The above suggestion seems to have worked after doing some more
messing in the pom, and spending time doing RTFM and output logged by
release plugin.  See HBASE-5522 for the small change that seems to
have made the difference.  Check it out.

St.Ack

Thanks St.Ack. I don't see the test artifacts in [1] yet but that could be
because it takes a few hours for the bits to propagate. I will check again
later today/early tomorrow and if everything works will drop a note for
confirmation.

[1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/

Thanks,
Arvind

On Tue, Mar 6, 2012 at 11:05 AM, Stack <[EMAIL PROTECTED]> wrote:

> On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]>
> wrote:
> > 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.
> >
>
> The above suggestion seems to have worked after doing some more
> messing in the pom, and spending time doing RTFM and output logged by
> release plugin.  See HBASE-5522 for the small change that seems to
> have made the difference.  Check it out.
>
> St.Ack
>

2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
> Thanks St.Ack. I don't see the test artifacts in [1] yet but that could be
> because it takes a few hours for the bits to propagate. I will check again
> later today/early tomorrow and if everything works will drop a note for
> confirmation.
>
> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
>
> Thanks,
> Arvind

I saw the tests jar. Yey... more happy coders.

Thanks St.Ack,

> On Tue, Mar 6, 2012 at 11:05 AM, Stack <[EMAIL PROTECTED]> wrote:
>
>> On Mon, Mar 5, 2012 at 3:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]>
>> wrote:
>> > 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.
>> >
>>
>> The above suggestion seems to have worked after doing some more
>> messing in the pom, and spending time doing RTFM and output logged by
>> release plugin.  See HBASE-5522 for the small change that seems to
>> have made the difference.  Check it out.
>>
>> St.Ack
>>

--
Ioan Eugen Stan
http://ieugen.blogspot.com/

On Tue, Mar 6, 2012 at 12:15 PM, Ioan Eugen Stan <[EMAIL PROTECTED]> wrote:
> 2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
>> Thanks St.Ack. I don't see the test artifacts in [1] yet but that could be
>> because it takes a few hours for the bits to propagate. I will check again
>> later today/early tomorrow and if everything works will drop a note for
>> confirmation.
>>
>> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
>>
>> Thanks,
>> Arvind
>
> I saw the tests jar. Yey... more happy coders.
>

Sweet. Thanks for the help and the poking all.
St.Ack

On Tue, Mar 6, 2012 at 12:23 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Tue, Mar 6, 2012 at 12:15 PM, Ioan Eugen Stan <[EMAIL PROTECTED]>
> wrote:
> > 2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
> >> Thanks St.Ack. I don't see the test artifacts in [1] yet but that could
> be
> >> because it takes a few hours for the bits to propagate. I will check
> again
> >> later today/early tomorrow and if everything works will drop a note for
> >> confirmation.
> >>
> >> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
> >>
> >> Thanks,
> >> Arvind
> >
> > I saw the tests jar. Yey... more happy coders.
> >
>

I can confirm too that the tests are now available and Sqoop is able to use
the correctly.

Thanks,
Arvind
>
> Sweet. Thanks for the help and the poking all.
> St.Ack
>

Hi,

Sorry, but I have bad news. I guess pushing the tests artifact did not do
the trick. Although we can see that
http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/ is populated
by the tests jar, I don't see it in
http://search.maven.org/#browse|1617628244. Also, in Sqoop and Hive, the
configuration :

   <dependency org="org.apache.hbase" name="hbase"
      rev="${hbase.version}" conf="hbase->default">
      <artifact name="hbase" type="jar"/>
      <artifact name="hbase" type="test-jar" ext="jar"
m:classifier="tests"/>

does not fetch the actual tests jar but fetches the normal jar. So sqoop
out of the box does not compile.

Eniss-MacBook-Pro:sqoop$ md5sum
build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
6cfa1bd84e00f8050f8d5dad59789e85
build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
Eniss-MacBook-Pro:sqoop$ md5sum
build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar
6cfa1bd84e00f8050f8d5dad59789e85
build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar

My uneducated guess would be that the parent hbase pom in maven repo was
not updated, so it does not know about the tests jar, which is deployed
later. But would be glad if anybody can shed some light.

Thanks,
Enis

On Tue, Mar 6, 2012 at 12:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]>wrote:

> On Tue, Mar 6, 2012 at 12:23 PM, Stack <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Mar 6, 2012 at 12:15 PM, Ioan Eugen Stan <[EMAIL PROTECTED]>
> > wrote:
> > > 2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
> > >> Thanks St.Ack. I don't see the test artifacts in [1] yet but that
> could
> > be
> > >> because it takes a few hours for the bits to propagate. I will check
> > again
> > >> later today/early tomorrow and if everything works will drop a note
> for
> > >> confirmation.
> > >>
> > >> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
> > >>
> > >> Thanks,
> > >> Arvind
> > >
> > > I saw the tests jar. Yey... more happy coders.
> > >
> >
>
> I can confirm too that the tests are now available and Sqoop is able to use
> the correctly.
>
> Thanks,
> Arvind
>
>
> >
> > Sweet. Thanks for the help and the poking all.
> > St.Ack
> >
>

On Thu, Mar 8, 2012 at 1:55 PM, Enis Söztutar <[EMAIL PROTECTED]> wrote:

> Hi,
>
> Sorry, but I have bad news. I guess pushing the tests artifact did not do
> the trick. Although we can see that
> http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/ is populated
> by the tests jar, I don't see it in
> http://search.maven.org/#browse|1617628244. Also, in Sqoop and Hive, the
> configuration :
>
>   <dependency org="org.apache.hbase" name="hbase"
>      rev="${hbase.version}" conf="hbase->default">
>      <artifact name="hbase" type="jar"/>
>      <artifact name="hbase" type="test-jar" ext="jar"
> m:classifier="tests"/>
>
> does not fetch the actual tests jar but fetches the normal jar. So sqoop
> out of the box does not compile.
>

I am not sure if this is true. Please see [1] for the build log from Sqoop
builds. Here is an excerpt from the same:
[ivy:resolve] downloading
http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/hbase-0.92.0-tests.jar
...
[ivy:resolve] ..........................................................
(1449kB)

You can actually see the hbase-0.92.0-tests.jar file in the Ivy cache
directory as well [2].

[1]
https://builds.apache.org/view/S-Z/view/Sqoop/job/Sqoop-ant-jdk-1.6/94/console
[2]
https://builds.apache.org/view/S-Z/view/Sqoop/job/Sqoop-ant-jdk-1.6/ws/build/ivy/lib/sqoop/hadoop23test/

Thanks,
Arvind

>
> Eniss-MacBook-Pro:sqoop$ md5sum
> build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
> 6cfa1bd84e00f8050f8d5dad59789e85
> build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
> Eniss-MacBook-Pro:sqoop$ md5sum
> build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar
> 6cfa1bd84e00f8050f8d5dad59789e85
> build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar
>
> My uneducated guess would be that the parent hbase pom in maven repo was
> not updated, so it does not know about the tests jar, which is deployed
> later. But would be glad if anybody can shed some light.
>
> Thanks,
> Enis
>
> On Tue, Mar 6, 2012 at 12:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]
> >wrote:
>
> > On Tue, Mar 6, 2012 at 12:23 PM, Stack <[EMAIL PROTECTED]> wrote:
> >
> > > On Tue, Mar 6, 2012 at 12:15 PM, Ioan Eugen Stan <
> [EMAIL PROTECTED]>
> > > wrote:
> > > > 2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
> > > >> Thanks St.Ack. I don't see the test artifacts in [1] yet but that
> > could
> > > be
> > > >> because it takes a few hours for the bits to propagate. I will check
> > > again
> > > >> later today/early tomorrow and if everything works will drop a note
> > for
> > > >> confirmation.
> > > >>
> > > >> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
> > > >>
> > > >> Thanks,
> > > >> Arvind
> > > >
> > > > I saw the tests jar. Yey... more happy coders.
> > > >
> > >
> >
> > I can confirm too that the tests are now available and Sqoop is able to
> use
> > the correctly.
> >
> > Thanks,
> > Arvind
> >
> >
> > >
> > > Sweet. Thanks for the help and the poking all.
> > > St.Ack
> > >
> >
>

Hi,

Right. The problem was that my local ivy cache contained the hbase parent
which does not know about the tests jar. So, if you have cached the 0.92
poms between 03/02 and 03/06, you have to delete that entry from your
cache. Still not seeing the tests jars in search.maven.org bothers me a
little, but it think it is best to focus on releasing 0.92.1 instead.

Thanks Arvind,
Enis

On Thu, Mar 8, 2012 at 2:13 PM, Arvind Prabhakar <[EMAIL PROTECTED]>wrote:

> On Thu, Mar 8, 2012 at 1:55 PM, Enis Söztutar <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > Sorry, but I have bad news. I guess pushing the tests artifact did not do
> > the trick. Although we can see that
> > http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/ is
> populated
> > by the tests jar, I don't see it in
> > http://search.maven.org/#browse|1617628244. Also, in Sqoop and Hive, the
> > configuration :
> >
> >   <dependency org="org.apache.hbase" name="hbase"
> >      rev="${hbase.version}" conf="hbase->default">
> >      <artifact name="hbase" type="jar"/>
> >      <artifact name="hbase" type="test-jar" ext="jar"
> > m:classifier="tests"/>
> >
> > does not fetch the actual tests jar but fetches the normal jar. So sqoop
> > out of the box does not compile.
> >
>
> I am not sure if this is true. Please see [1] for the build log from Sqoop
> builds. Here is an excerpt from the same:
>
>
> [ivy:resolve] downloading
>
> http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/hbase-0.92.0-tests.jar
> ...
> [ivy:resolve] ..........................................................
> (1449kB)
>
>
>
> You can actually see the hbase-0.92.0-tests.jar file in the Ivy cache
> directory as well [2].
>
> [1]
>
> https://builds.apache.org/view/S-Z/view/Sqoop/job/Sqoop-ant-jdk-1.6/94/console
> [2]
>
> https://builds.apache.org/view/S-Z/view/Sqoop/job/Sqoop-ant-jdk-1.6/ws/build/ivy/lib/sqoop/hadoop23test/
>
> Thanks,
> Arvind
>
>
>
> >
> > Eniss-MacBook-Pro:sqoop$ md5sum
> > build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
> > 6cfa1bd84e00f8050f8d5dad59789e85
> > build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0.jar
> > Eniss-MacBook-Pro:sqoop$ md5sum
> > build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar
> > 6cfa1bd84e00f8050f8d5dad59789e85
> > build/ivy/lib/sqoop/hadoop23test/hbase-0.92.0-tests.jar
> >
> > My uneducated guess would be that the parent hbase pom in maven repo was
> > not updated, so it does not know about the tests jar, which is deployed
> > later. But would be glad if anybody can shed some light.
> >
> > Thanks,
> > Enis
> >
> > On Tue, Mar 6, 2012 at 12:47 PM, Arvind Prabhakar <[EMAIL PROTECTED]
> > >wrote:
> >
> > > On Tue, Mar 6, 2012 at 12:23 PM, Stack <[EMAIL PROTECTED]> wrote:
> > >
> > > > On Tue, Mar 6, 2012 at 12:15 PM, Ioan Eugen Stan <
> > [EMAIL PROTECTED]>
> > > > wrote:
> > > > > 2012/3/6 Arvind Prabhakar <[EMAIL PROTECTED]>:
> > > > >> Thanks St.Ack. I don't see the test artifacts in [1] yet but that
> > > could
> > > > be
> > > > >> because it takes a few hours for the bits to propagate. I will
> check
> > > > again
> > > > >> later today/early tomorrow and if everything works will drop a
> note
> > > for
> > > > >> confirmation.
> > > > >>
> > > > >> [1] http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.92.0/
> > > > >>
> > > > >> Thanks,
> > > > >> Arvind
> > > > >
> > > > > I saw the tests jar. Yey... more happy coders.
> > > > >
> > > >
> > >
> > > I can confirm too that the tests are now available and Sqoop is able to
> > use
> > > the correctly.
> > >
> > > Thanks,
> > > Arvind
> > >
> > >
> > > >
> > > > Sweet. Thanks for the help and the poking all.
> > > > St.Ack
> > > >
> > >
> >
>