diff options
| author | Yin Huai <yhuai@databricks.com> | 2016-12-21 09:26:13 -0800 |
|---|---|---|
| committer | Yin Huai <yhuai@databricks.com> | 2016-12-21 09:26:13 -0800 |
| commit | 1a64388973711b4e567f25fa33d752066a018b49 (patch) | |
| tree | bad66c13fc70630e762db38b24d91bc1bc4632a8 /pom.xml | |
| parent | b7650f11c7afbdffc6f5caaafb5dcfd54f7a25ff (diff) | |
| download | spark-1a64388973711b4e567f25fa33d752066a018b49.tar.gz spark-1a64388973711b4e567f25fa33d752066a018b49.tar.bz2 spark-1a64388973711b4e567f25fa33d752066a018b49.zip | |
[SPARK-18951] Upgrade com.thoughtworks.paranamer/paranamer to 2.6
## What changes were proposed in this pull request?
I recently hit a bug of com.thoughtworks.paranamer/paranamer, which causes jackson fail to handle byte array defined in a case class. Then I find https://github.com/FasterXML/jackson-module-scala/issues/48, which suggests that it is caused by a bug in paranamer. Let's upgrade paranamer. Since we are using jackson 2.6.5 and jackson-module-paranamer 2.6.5 use com.thoughtworks.paranamer/paranamer 2.6, I suggests that we upgrade paranamer to 2.6.
Author: Yin Huai <yhuai@databricks.com>
Closes #16359 from yhuai/SPARK-18951.
Diffstat (limited to 'pom.xml')
| -rw-r--r-- | pom.xml | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -179,7 +179,7 @@ <antlr4.version>4.5.3</antlr4.version> <jpam.version>1.1</jpam.version> <selenium.version>2.52.0</selenium.version> - <paranamer.version>2.8</paranamer.version> + <paranamer.version>2.6</paranamer.version> <maven-antrun.version>1.8</maven-antrun.version> <commons-crypto.version>1.0.0</commons-crypto.version> @@ -1863,6 +1863,11 @@ </exclusion> </exclusions> </dependency> + <dependency> + <groupId>com.thoughtworks.paranamer</groupId> + <artifactId>paranamer</artifactId> + <version>${paranamer.version}</version> + </dependency> </dependencies> </dependencyManagement> |