Clojars now requires a license in the POM for new projects or projects that already specify a license Hi all! Clojars (https://clojars.org - the community repository for open source Clojure libraries) will now require a license to be specified in the POM file for: - newly uploaded versions for new projects - newly uploaded versions for existing projects where the prior version had a license We will then start requiring a license for all newly uploaded versions on or after 2024-01-01. Note that this will not impact any existing versions; existing versions that don't have a license in the POM file will remain unchanged. For more details, see https://github.com/clojars/clojars-web/issues/873 for discussion of the change, and the https://github.com/clojars/clojars-web/wiki/Pushing#licenses for how to add a license to your POM. Why is Clojars making this change? We are making this change: - to better support auditing from java ecosystem tools that use the POM as the source of truth for the license - enforce better hygiene; all open source projects should have a license How does this change impact me? If you only consume projects from Clojars and do not release libraries, you don't need to do anything. If you publish projects to Clojars, you will need to: - include a license with any new projects - continue to include a license with new versions of projects where you already provide a license - update any projects that don't provide a license to provide one before the end of the year if you plan to release a new version If Clojars rejects your deploy, you will see a message like:

Could not transfer metadata org.clojars.tcrawley:deploytest/maven-metadata.xml from/to clojars (): authorization failed for , status: 403 Forbidden - the POM file does not include a license. See