[
https://issues.apache.org/jira/browse/HADOOP-9613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218130#comment-15218130
]
Sean Busbey commented on HADOOP-9613:
-------------------------------------
I manually started a precommit run. Toggling the patch available status (or
otherwise updating the issue without changing the most recent attachment) won't
cause a new run because the Precommit Admin job that coordinates grabbing stuff
from JIRA keeps track of patches it has sent for work before and skips them.
To manually re-run, someone with a builds.apache login (which can be any
committer given PMC sign-off) goes to, e.g. [the HADOOP precommit
job|https://builds.apache.org/view/PreCommit%20Builds/job/PreCommit-HADOOP-Build/]
and then enters the numeric part of the JIRA id.
> [JDK8] Update jersey version to latest 1.x release
> --------------------------------------------------
>
> Key: HADOOP-9613
> URL: https://issues.apache.org/jira/browse/HADOOP-9613
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build
> Affects Versions: 2.4.0, 3.0.0
> Reporter: Timothy St. Clair
> Assignee: Tsuyoshi Ozawa
> Labels: maven
> Attachments: HADOOP-2.2.0-9613.patch,
> HADOOP-9613.004.incompatible.patch, HADOOP-9613.005.incompatible.patch,
> HADOOP-9613.006.incompatible.patch, HADOOP-9613.007.incompatible.patch,
> HADOOP-9613.008.incompatible.patch, HADOOP-9613.009.incompatible.patch,
> HADOOP-9613.010.incompatible.patch, HADOOP-9613.011.incompatible.patch,
> HADOOP-9613.012.incompatible.patch, HADOOP-9613.013.incompatible.patch,
> HADOOP-9613.1.patch, HADOOP-9613.2.patch, HADOOP-9613.3.patch,
> HADOOP-9613.patch
>
>
> Update pom.xml dependencies exposed when running a mvn-rpmbuild against
> system dependencies on Fedora 18.
> The existing version is 1.8 which is quite old.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
