Fork me on GitHub
#tools-deps
<
2018-10-01
>
krukow14:10:21

@seancorfield thanks for helping out - I ended up with this uberjar command:

:uberjar
  {:extra-deps
   {luchiniatwork/cambada {:mvn/version "1.0.0"}}
   :main-opts ["-m" "cambada.uberjar"
               "-m" "vsts-flow-metrics.cli"]}}
which should help for the main warning. Then without specifying a :mvn/repos in deps.edn I get:
Exception in thread "main" org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.httpcomponents:httpcore:jar:4.4.9
	at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:323)
...
	at clojure.tools.deps.alpha$resolve_deps.invoke(alpha.clj:197)
	at cambada.uberjar$get_dep_jars.invokeStatic(uberjar.clj:109)
But If deps.edn contain
:mvn/repos {"central" {:url ""}
             "clojars" {:url ""}}
the command completes

krukow14:10:31

I'll see if I can create a minimal repro

krukow14:10:53

and I use clj -A:uberjar -Srepro -Sforce to create the uberjar

timgilbert14:10:42

Say, using an s3p private repo I get a lot of messages like these when starting clojure: Downloading: com/amazonaws/aws-java-sdk-dynamodb/maven-metadata.xml from Apparently this file is just missing, but I definitely don't have it in my private repo. Is there any way to tell clojure and/or maven to only use the private repo for artifacts from a specific namespace?

timgilbert16:10:32

Alternately, is there a way to suppress that message from appearing? It's not so good for shell-script type tasks

timgilbert16:10:19

The full panoply of messages is more like this:

Downloading: com/google/code/findbugs/jsr305/maven-metadata.xml from 
Downloading: com/google/guava/guava/maven-metadata.xml from 
Downloading: commons-codec/commons-codec/maven-metadata.xml from 
Downloading: com/amazonaws/aws-java-sdk-cloudwatch/maven-metadata.xml from 
Downloading: com/amazonaws/aws-java-sdk-dynamodb/maven-metadata.xml from 
Downloading: com/amazonaws/aws-java-sdk-kinesis/maven-metadata.xml from 
Downloading: com/amazonaws/amazon-kinesis-client/maven-metadata.xml from 

timgilbert16:10:43

I guess what I'd like is the ability to set the <updatePolicy> value on my S3 repository to never, which I think would make this behavior go away. http://maven.apache.org/pom.html#Repositories

zane19:10:48

:jvm-opts isn't a valid top-level key, right? Only inside an alias in :aliases?

alexmiller19:10:23

there is a ticket wrt default jvm-opts

zane20:10:28

Okay. Thanks, Alex!