just curious but is it possible to pull dependencies from a Google Cloud Storage based maven repo ?

if it acts as a Maven repo on http, then sure

if not, then no

how do you configure it in Maven?

if there's a custom wagon, then that will not work

but it could be made to do so

need to research more. Currently I have a jar that is being built/published by gradle into GCS using there maven-publish plugin. Basically to avoid managing some private artifact repository and just use GCS

sure, this is commonly done with s3 (and tools.deps includes support for that)

I'm modifying depstar to insert a MANIFEST.MF file and pom.xml / pom.properties. My minimalist thinking is that it should do this automatically if it finds a pom.xml file in the directory in which it is run -- as part of the project you are building a JAR/uberjar for. Is this a good idea and if not, why not?

I'm thinking you'd do clj -Spom && clj -A:jar my-project.jar (assuming the :jar alias brings in depstar and uses -m hf.depstar.jar).

Are there situations where automatically picking up the local pom.xml file is a bad idea? Are there situations where you would want to use a different file as the POM or you might have the POM in a different location?

Not directly answering your question, but any changes to depstar that allow me to java -jar foo.jar rather than java -cp foo.jar clojure.main -m foo.core would be useful.

@dorab that would require depstar to deal with AOT -- not happening.

What this change will allow for is java -jar foo.jar -m your.entry.point instead of java -cp foo.jar clojure.main -m your.entry.point

(assuming you had pom.xml locally -- so depstar would generate a manifest and because you're generating an uberjar, instead of a library JAR, you'd get Main-Class: clojure.main added)

I guess my real question is whether it would be useful/important to add a flag to suppress consumption of pom.xml?

(easy enough to do, so I might as well)

Java doesn’t care about the pom stuff so that seems harmless. clj will use it to find dependencies though if you use it as a local file dep

That’s prob good if not an uberjar and bad if it is an uberjar

(As you’d get deps from two places on the classpath)

Yeah, that's why this has cropped up -- http://cljdoc.org assumes the JAR contains it.

And with that ... seancorfield/depstar "0.3.0" is available!

@seancorfield java -jar foo.jar -m your.entry.point is good enough for me. Thanks for the release. Will try it out.