spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nadav Samet (JIRA)" <>
Subject [jira] [Created] (SPARK-24074) Maven package resolver downloads javadoc instead of jar
Date Tue, 24 Apr 2018 22:25:00 GMT
Nadav Samet created SPARK-24074:

             Summary: Maven package resolver downloads javadoc instead of jar
                 Key: SPARK-24074
             Project: Spark
          Issue Type: Bug
          Components: Spark Submit
    Affects Versions: 2.3.0
         Environment: {code:java}
// code placeholder
            Reporter: Nadav Samet

// code placeholder
>From some reason spark downloads a javadoc artifact of a package instead of the jar.

Steps to reproduce:
 # Delete (or move) your local ~/.ivy2 cache to force Spark to resolve and fetch artifacts
from central:

rm -rf ~/.ivy2

 # Run:

~/dev/spark-2.3.0-bin-hadoop2.7/bin/spark-shell --packages org.scalanlp:breeze_2.11:0.13.2{code}

 # Spark would download the javadoc instead of the jar:
[SUCCESSFUL ] net.sourceforge.f2j#arpack_combined_all;0.1!arpack_combined_all.jar (610ms){code}

 # Later spark would complain that it couldn't find the jar:

Warning: Local jar /Users/thesamet/.ivy2/jars/net.sourceforge.f2j_arpack_combined_all-0.1.jar
does not exist, skipping.
Setting default log level to "WARN".
To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use setLogLevel(newLevel).{code}

 # The dependency of breeze on f2j_arpack_combined seem fine: []


This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message