pystorm / streamparse

Run Python in Apache Storm topologies. Pythonic API, CLI tooling, and a topology DSL.
http://streamparse.readthedocs.io/
Apache License 2.0
1.5k stars 218 forks source link

Unable to run 'lein deps :tree'! #472

Open tanjiarui opened 4 years ago

tanjiarui commented 4 years ago

Hello streamparse, I'm totally new to this tool, so there was an error which I couldn't understand when I tried to run the word count example. 2019-12-31 17-15-35屏幕截图 Here are my dependencies: Oracle JDK 13.0.1 Lein 2.9.0 Storm 2.1.0 Plus, config.json and project.clj had been adjusted as the tutorial indicated. Many thanks for your help!! Best regards, Terry

leonkozlowski commented 4 years ago

I am also running into this will the sparse quickstart

RuntimeError: Unable to run 'lein deps :tree'!
STDOUT:

STDERR:
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
Tried to use insecure HTTP repository without TLS:
 repository.jboss.org: http://repository.jboss.org/nexus/content/groups/public/
 net/minidev/json-smart/maven-metadata.xml

This is almost certainly a mistake; for details see
https://github.com/technomancy/leiningen/blob/master/doc/FAQ.md
lyhanburger commented 4 years ago

I am also running into this will the sparse quickstart

RuntimeError: Unable to run 'lein deps :tree'!
STDOUT:

STDERR:
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
Tried to use insecure HTTP repository without TLS:
 repository.jboss.org: http://repository.jboss.org/nexus/content/groups/public/
 net/minidev/json-smart/maven-metadata.xml

This is almost certainly a mistake; for details see
https://github.com/technomancy/leiningen/blob/master/doc/FAQ.md

I also occur it then i find it: https://github.com/technomancy/leiningen/blob/stable/doc/FAQ.md i rewrite my project.clj like 👇

(defproject wordcount "0.0.1-SNAPSHOT"
  :resource-paths ["_resources"]
  :target-path "_build"
  :min-lein-version "2.0.0"
  :jvm-opts ["-client"]
  :dependencies  [[org.apache.storm/storm-core "2.2.0"]
                  [org.apache.storm/flux-core "2.2.0"]]
  :jar-exclusions     [#"log4j\.properties" #"org\.apache\.storm\.(?!flux)" #"trident" #"META-INF" #"meta-inf" #"\.yaml"]
  :uberjar-exclusions [#"log4j\.properties" #"org\.apache\.storm\.(?!flux)" #"trident" #"META-INF" #"meta-inf" #"\.yaml"]
  )
(require 'cemerick.pomegranate.aether)
(cemerick.pomegranate.aether/register-wagon-factory!
 "http" #(org.apache.maven.wagon.providers.http.HttpWagon.))

it worked for me

nils-braun commented 3 years ago

Thanks for the solution! While this certainly works, it also opens up quite some security risk :-/ I am wondering if the root cause can be fixed, because as far as I see the repository.jboss.org does offer a "normal" https entry. Does someone know from where this repository.jboss.org dependency comes?