Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/940#issuecomment-50303013
@witgo Thanks for checking the dependencies on the JIRA page! I list the
dependency graph here so other people can see the difference easily. I think we
need to figure out the following:
* Which part of breeze needs commons-math3? The problem with commons-math3
is that hadoop 2.3 and 2.4 depend on commons-math3-3.1.1, which is not fully
compatible with 3.2.
@dlwh Could you help answer this and what is the plan for the 0.9 release?
I saw you updated the version to `0.9-SNAPSHOT`.
* Is `org.scalamacros:quasiquotes` a problem? @marmbrus
breeze-0.7
~~~
+-org.scalanlp:breeze_2.10:0.7 [S]
+-com.github.fommil.netlib:core:1.1.2
+-com.github.rwl:jtransforms:2.4.0
| +-junit:junit:4.8.2
|
+-com.thoughtworks.paranamer:paranamer:2.2
+-com.typesafe:scalalogging-slf4j_2.10:1.0.1
| |
| +-org.slf4j:slf4j-api:1.7.2
|
+-net.sf.opencsv:opencsv:2.3
+-net.sourceforge.f2j:arpack_combined_all:0.1
+-org.apache.commons:commons-math3:3.2
+-org.scalanlp:breeze-macros_2.10:0.3 [S]
|
+-org.spire-math:spire_2.10:0.7.1 [S]
|
+-org.spire-math:spire-macros_2.10:0.7.1 [S]
~~~
breeze-0.8.1
~~~
+-org.scalanlp:breeze_2.10:0.8.1 [S]
+-com.github.fommil.netlib:core:1.1.2
+-com.github.rwl:jtransforms:2.4.0
| +-junit:junit:4.8.2
|
+-com.typesafe.scala-logging:scala-logging-slf4j_2.10:2.1.2 [S]
| |
| +-com.typesafe.scala-logging:scala-logging-api_2.10:2.1.2 [S]
| |
| +-org.slf4j:slf4j-api:1.7.7
|
+-net.sf.opencsv:opencsv:2.3
+-net.sourceforge.f2j:arpack_combined_all:0.1
+-org.apache.commons:commons-math3:3.2
+-org.scalanlp:breeze-macros_2.10:0.3.1 [S]
| |
| +-org.scalamacros:quasiquotes_2.10:2.0.0 [S]
|
+-org.spire-math:spire_2.10:0.7.4 [S]
|
+-org.scalamacros:quasiquotes_2.10:2.0.0 [S]
|
+-org.spire-math:spire-macros_2.10:0.7.4 [S]
+-org.scalamacros:quasiquotes_2.10:2.0.0 [S]
~~~
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
