I even got this email > User ‘holyjak’ was added to the org.scicloj group with scope ‘*’ by scicloj.

does your artifact have a license? See https://clojureverse.org/t/ann-clojars-now-requires-a-license-in-the-pom-for-new-projects-or-projects-that-already-specify-a-license/10347/4?u=tcrawley

unfortunately, a missing license just gives a 403, https://clojurians.slack.com/archives/C0H28NMAS/p1717155058719789. I also got bit by this recently

ah, thx! 👀

Hm, I have added the license now but still getting 403. Part of META-INF/maven/org.scicloj/wolframite/pom.xml :

<repositories>
    <repository>
      <id>clojars</id>
      <url></url>
    </repository>
  </repositories>
  <licenses>
    <license>
      <name>Eclipse Public License 2.0</name>
      <url></url>
    </license>
    <organization>SciCloj</organization>
  </licenses>
</project>

I don't think you can have in the list (from the log on clojars): "invalid pom file: Unrecognised tag: 'organization' (position: START_TAG seen ...</license>\\n <organization>... @45:19)"

Also, what tooling are you using to deploy?

It succeeded now! Many thanks! And to answer, Slipset’s deploy lib for deps

Interesting. I wonder what version of the maven/aether lib that is pulling in that prevents you from seeing the extended status message? It would have been helpful to see, since it would have told you to add a license (though the latter error would not have been reported that way). What version of the lib are you using?

@U7RJTCH6J What were you deploying with when you didn't see the status message either?

also slipset's deploy lib

slipset/deps-deploy {:mvn/version "RELEASE"}

I use slipset/deps-deploy {:mvn/version "0.2.2"} It uses

clj-commons/pomegranate {:mvn/version "1.2.23"}
        s3-wagon-private/s3-wagon-private {:mvn/version "1.3.5"}

The latest is using a new enough pomegranate to bring in the maven dep that fixes status messages, so I'm not sure why it isn't seen. Would one of y'all be willing to share the full output of a deploy where the license wasn't set (if you still have it)?

FYI @U04V5VAUN ☝️

I guess this one

Deploying org.scicloj/wolframite-1.0.0-SNAPSHOT to repository clojars as holyjak
Could not find metadata org.scicloj:wolframite:1.0.0-SNAPSHOT/maven-metadata.xml in clojars ()
Sending org/scicloj/wolframite/1.0.0-SNAPSHOT/wolframite-1.0.0-20240701.164820-1.pom (1k)
    to 
Sending org/scicloj/wolframite/1.0.0-SNAPSHOT/wolframite-1.0.0-20240701.164820-1.jar (750k)
    to 
Could not find metadata org.scicloj:wolframite/maven-metadata.xml in clojars ()
Sending org/scicloj/wolframite/1.0.0-SNAPSHOT/maven-metadata.xml (1k)
    to 
Sending org/scicloj/wolframite/maven-metadata.xml (1k)
    to 
Could not transfer metadata org.scicloj:wolframite/maven-metadata.xml from/to clojars (): authorization failed for , status: 403 Forbidden
Execution error (AuthorizationException) at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon/put (AbstractHttpClientWagon.java:817).
authorization failed for , status: 403 Forbidden

Full report at:
/var/folders/p7/mlz1j06x5bqb66w404xrkgzh0000gn/T/clojure-13640841608032815673.edn

nothing useful here either…

Thanks @U0522TWDA! would you be willing to run clojure -A:deploy -Stree and share that output (assuming you bring in deps-deploy via an alias called :deploy)?

sure!

Thanks! The wagon-http version looks correct. I just updated the dev dependency that clojars has on pomegranate to the same as above (1.2.23), and all the tests pass. The tests rely on pomegranate (via wagon-http) passing the status message through, so I'm not sure what is going on here. I'll have to do more digging.

I created https://github.com/clojars/clojars-web/issues/885 to dig in to it more later.