These changes have now been completed - you will need to use a verified group
when deploying a *new* project to Clojars. These changes will only impact folks
deploying to Clojars; consumption of artifacts from Clojars is unchanged. A
summary of the current state:
- *existing* projects can still
A followup on:
On Monday, March 1, 2021 at 8:47:05 AM UTC-5 Toby Crawley wrote:
> # Dropping support for old Java versions
>
> The repository itself is hosted behind a Fastly CDN, and Fastly is forcing
> all accounts to switch to SNI[1] for TLS connections. Clojars will be
> migrated on or aft
On Mon, Mar 1, 2021, at 11:08, James Reeves wrote:
> Have you considered automatically validating domain name ownership by
> supplying a challenge token and then looking for it at a well-known location
> on the domain?
That's a good suggestion - I have considered that as a verification option. T
This is an interesting change, and essentially enforces a de-facto package
naming scheme for Clojure. I don't see this as a bad thing, though.
Have you considered automatically validating domain name ownership by supplying
a challenge token and then looking for it at a well-known location on the
Howdy folks! We have two separate changes coming for the Clojars system that
you need to be aware of.
First, the tl;dr:
- After 2021-04-15, versions of Java older than 7u25 will no longer be able to
access the Clojars repository
- After 2021-04-18, a Clojars group name must have verified owne
