Repository: spark
Updated Branches:
  refs/heads/branch-1.6 f445cce94 -> 03913af30


[SPARK-16751][HOTFIX] Also update hadoop-1 deps file to reflect derby 10.12.1.1 
security fix

## What changes were proposed in this pull request?

See https://github.com/apache/spark/pull/14379 ; I failed to note in 
back-porting to 1.6 that an additional Hadoop 1 deps file would need to be 
updated. This makes that change.

## How was this patch tested?

Jenkins tests.

Author: Sean Owen <[email protected]>

Closes #14403 from srowen/SPARK-16751.2.


Project: http://git-wip-us.apache.org/repos/asf/spark/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark/commit/03913af3
Tree: http://git-wip-us.apache.org/repos/asf/spark/tree/03913af3
Diff: http://git-wip-us.apache.org/repos/asf/spark/diff/03913af3

Branch: refs/heads/branch-1.6
Commit: 03913af30bc0f000dcdcff768ba1625952270ef4
Parents: f445cce
Author: Sean Owen <[email protected]>
Authored: Fri Jul 29 09:06:34 2016 -0700
Committer: Sean Owen <[email protected]>
Committed: Fri Jul 29 09:06:34 2016 -0700

----------------------------------------------------------------------
 dev/deps/spark-deps-hadoop-1 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/spark/blob/03913af3/dev/deps/spark-deps-hadoop-1
----------------------------------------------------------------------
diff --git a/dev/deps/spark-deps-hadoop-1 b/dev/deps/spark-deps-hadoop-1
index 573431b..dd5a6dc 100644
--- a/dev/deps/spark-deps-hadoop-1
+++ b/dev/deps/spark-deps-hadoop-1
@@ -53,7 +53,7 @@ curator-recipes-2.4.0.jar
 datanucleus-api-jdo-3.2.6.jar
 datanucleus-core-3.2.10.jar
 datanucleus-rdbms-3.2.9.jar
-derby-10.10.1.1.jar
+derby-10.12.1.1.jar
 eigenbase-properties-1.1.5.jar
 geronimo-annotation_1.0_spec-1.1.1.jar
 geronimo-jaspic_1.0_spec-1.0.jar


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to