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
Hadoop tests aren't failing, Cascading tests fail because the Hadoop 1.0.0 pom
does not declare all its runtime dependencies as the previous pom's did.
Do what you will.
ckw
On Dec 23, 2011, at 1:50 PM, Matt Foley wrote:
> Hi Chris,
> Please open a jira and post the specific test(s) that are
And I also vote +1.
I am delighted to announce that the Release 1.0.0 vote has passed, with
count:
+1: 6 votes, including 3 PMC members
-1: no votes
The publication process is underway, and I will announce it on
general@tomorrow, after the required propagation time.
Best regards,
--Ma
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 (
Hi Chris,
Please open a jira and post the specific test(s) that are failing, and
we'll try to help track it down.
Since no one else posted problems, and the RC did pass our system tests,
I'm going to go ahead
and declare the vote accepted. If this turns out to be something serious,
we can spin a p
Different versions of the patch are supposed to have the same name, and
could be sorted by date.
A different name should be used to indicate the target branch.
See the "Naming your patch" section on
http://wiki.apache.org/hadoop/HowToContribute
Cheers,
Joep
On Fri, Dec 23, 2011 at 12:13 PM, Pat
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
You can find actual committed files from 'Subversion Commits' in JIRA.
Mostly latest patch will be committed. Also you can check on which path,
reviewers given +1.
I feel Subversion Commits is correct option.
hope it will help you...
Regards,
Uma
From:
Hi,
How do I know the code changed with a particular JIRA? If I go to
MAPREDUCE-1943, there are multiple patch attachments. Should I go with the
date and pick the latest patch?
Is there any other way to identify the changes done to the code with a
particular JIRA?
Regards,
Praveen
