Clojurians Log v2
clojure 2025-12-31
Two of my uploads to Maven Central failed yesterday on validation rules that I did not upload Javadoc. These are of course Clojure projects with aot compiled classes and there is no Java and no Javadoc. One was tools.reader which we've been uploading since 2012 without issue. I contacted support and they have a new rule that any jar with class files needs source and Javadoc jars, but it's ok if they are empty. So I need to burn my time making a build, cpu to make an empty jar, bandwidth to upload it, and storage to save it in their repo, for literally no purpose. Sorry, just needed to rant. :)
Are these puns helping or hurting?
Did they attempt to explain why they added this pointless rule? If those JAR files can be empty, it seems to have negative value for security or anything else...
Weirdly, this seven-year-old StackOverflow Q&A seems to cover this scenario: https://stackoverflow.com/questions/53706943/how-to-upload-an-artifact-to-maven-central-with-an-empty-javadoc-jar-or-empty-s?utm_source=copilot.com
I have solutions for this elsewhere, it's not that big a deal, just dumb
Burned us on Datomic releases too
By the way, those jars on Maven are a major convenience for the time-honored way of building apps, which I hope will keep working forever so the build processes won't have to be revisited... However, doesn't the deps.edn thing also fetch dependencies from (any) Git repository? Is there a grand plan to facilitate (or does this already exist?) an ecosystem where no Maven server is relevant?
no, there is no plan to change the way contribs are released and consumed via Maven