hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris K Wensel <ch...@wensel.net>
Subject Re: [VOTE] Hadoop-1.0.0 release candidate 3
Date Sat, 24 Dec 2011 00:57:00 GMT
I simply added the jax-rs jsr mvn runtime dependency to my test runtime, but it isn't my dependency,
it is hadoop's.

worked before in previous releases, doesn't work now in 1.0 without extra steps on my part
(and likely others downstream). 

just sayin'...

ckw

On Dec 23, 2011, at 2:03 PM, Luke Lu wrote:

> That's because of the missing jersey dependencies in hadoop-core pom
> and that you're using the minicluster stuff that will pull in the
> webhdfs classes. A work around would be adding jersey-* dependencies
> (cf. hadoop ivy.xml) to your pom in test scope.
> 
> There is no perfect solution to this problem (as long as we have only
> one hadoop-core artifact), as you don't want to add server
> dependencies in hadoop core pom, when common downstream usage is just
> the client stuff.
> 
> On Fri, Dec 23, 2011 at 10:28 AM, Chris K Wensel <chris@wensel.net> wrote:
>> fwiw, still seeing some dependency issues preventing Cascading tests from passing.
>> 
>> I've only changed mvn dependencies from 20.2 to 1.0.0 and now see
>> 
>> java.io.IOException: java.lang.NoClassDefFoundError: javax/ws/rs/core/StreamingOutput
>> 
>> jackson is now indeed being pulled down and included.
>> 
>> ckw
>> 
>> On Dec 20, 2011, at 1:57 PM, Matt Foley wrote:
>> 
>>> Chris, thank you very much for bringing this to our attention!
>>> In Nexus, it appears necessary to explicitly "drop" the previous release
>>> candidate before it will show a newer one.  I have now done so, and the
>>> artifacts at
>>> 
>>> https://repository.apache.org/content/groups/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>> are now correctly dated Dec 16.
>>> 
>>> Apologies to anyone who inadvertently obtained the old artifacts from the
>>> maven repo.
>>> Thanks,
>>> --Matt
>>> 
>>> On Tue, Dec 20, 2011 at 12:09 PM, Roman Shaposhnik <rvs@apache.org> wrote:
>>> 
>>>> Try the following maven version: 1.0.0rc3
>>>> 
>>>> Those artifacts are available.
>>>> 
>>>> Thanks,
>>>> Roman.
>>>> 
>>>> 
>>>> On Tue, Dec 20, 2011 at 11:05 AM, Chris K Wensel <chris@wensel.net>
wrote:
>>>>> Which maven repo was updated?
>>>>> 
>>>>> Not seeing anything new in the staging repo
>>>>> 
>>>> https://repository.apache.org/content/repositories/staging/org/apache/hadoop/hadoop-core/1.0.0/
>>>>> 
>>>>> File dates are Dec 9th.
>>>>> 
>>>>> ckw
>>>>> 
>>>>> On Dec 16, 2011, at 12:10 PM, Matt Foley wrote:
>>>>> 
>>>>>> Hello all,
>>>>>> I have posted a new release candidate for Hadoop 1.0.0 at
>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc3/
>>>>>> 
>>>>>> Please download, evaluate, and vote on this list.
>>>>>> The artifacts have also been posted to the maven repo.
>>>>>> The vote will close at 12:30pm PST on Friday 13 Dec.
>>>>>> 
>>>>>> There had been an issue raised regarding
>>>>>> HADOOP-7929<https://issues.apache.org/jira/browse/HADOOP-7929>.
>>>>>> This has been evaluated and the jira closed as invalid.  Thanks to
>>>> Andrew
>>>>>> and others involved for helping assure the quality of this release.
>>>>>> 
>>>>>> As previously mentioned, use of JDK 1.6.0_26 or better is recommended
>>>> for
>>>>>> this release.
>>>>>> 
>>>>>> Thank you,
>>>>>> 
>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as 0.20.205.1)
>>>>>> 
>>>>>> 
>>>>>> On Fri, Dec 16, 2011 at 12:32 AM, Matt Foley <mfoley@hortonworks.com>
>>>> wrote:
>>>>>> 
>>>>>>> Dear all,
>>>>>>> I have a clean build of the below, that passes junit testing,
and was
>>>>>>> about to post it, when I got email about the newly opened HADOOP-7929<
>>>> https://issues.apache.org/jira/browse/HADOOP-7929> "Port
>>>>>>> HADOOP-7070 to branch-1".  It appears this prevents secure HBase
from
>>>>>>> working with secure Hadoop.  Since HBase support is a key element
of
>>>> 1.0.0,
>>>>>>> and it seems this will be fixable fairly promptly, I am going
to wait
>>>>>>> another day for 1.0.0-rc3.
>>>>>>> 
>>>>>>> Thanks for your patience,
>>>>>>> --Matt
>>>>>>> 
>>>>>>> 
>>>>>>> On Tue, Dec 13, 2011 at 6:17 PM, Matt Foley <mfoley@hortonworks.com
>>>>> wrote:
>>>>>>> 
>>>>>>>> In various emails and jiras, I have been asked to incorporate
the
>>>>>>>> following additional patches in 1.0.0:
>>>>>>>> 
>>>>>>>>  - MAPREDUCE-3319 (Roman)
>>>>>>>>  - HADOOP-7903 (Arpit)
>>>>>>>>  - MAPREDUCE-3475 (Daryn)
>>>>>>>>  - HDFS-2589 (Daryn)
>>>>>>>>  - HADOOP jira about to be opened (Chris W.) for missing
jackson
>>>>>>>>  dependency in hadoop pom.
>>>>>>>> 
>>>>>>>> I have not heard of any other significant issues in this
build.
>>>>>>>> I will re-spin the release candidate tomorrow.
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> --Matt
>>>>>>>> 
>>>>>>>> On Thu, Dec 8, 2011 at 11:57 AM, Matt Foley <mattf@apache.org>
wrote:
>>>>>>>> 
>>>>>>>>> Hello all,
>>>>>>>>> I have posted a release candidate for Hadoop 1.0.0 at
>>>>>>>>>   http://people.apache.org/~mattf/hadoop-1.0.0-rc2/
>>>>>>>>> 
>>>>>>>>> Please download, evaluate, and vote on this list.
>>>>>>>>> The artifacts will be posted to the maven repo shortly.
>>>>>>>>> The vote will close at noon PST on Thursday 15 Dec.
>>>>>>>>> 
>>>>>>>>> It may be of interest that it is important to use an
appropriate
>>>> version
>>>>>>>>> of Java.
>>>>>>>>> I lost several days due to instabilities apparently in
Oracle JDK
>>>>>>>>> 1.6.0_23, which
>>>>>>>>> caused about 30 junit test failures in contrib (streaming,
>>>> schedulers,
>>>>>>>>> and gridmix).
>>>>>>>>> Switching to JDK 1.6.0_26 made the problems go away.
>>>>>>>>> 
>>>>>>>>> The release artifacts in this hadoop-1.0.0-rc2 were build
with
>>>>>>>>> JDK 1.6.0_26.
>>>>>>>>> 
>>>>>>>>> Thank you,
>>>>>>>>> --Matt (Release Manager for 1.0.0, formerly known as
0.20.205.1)
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> --
>>>>> Chris K Wensel
>>>>> chris@concurrentinc.com
>>>>> http://concurrentinc.com
>>>>> 
>>>> 
>> 
>> --
>> Chris K Wensel
>> chris@concurrentinc.com
>> http://concurrentinc.com
>> 

--
Chris K Wensel
chris@concurrentinc.com
http://concurrentinc.com


Mime
View raw message