James Reeves

I was moving the libraries over as Clojars changed its policy around artifact group names, moving away from arbitrary group IDs and toward verifiable domain names. This seemed like a...

Ah, I see there's an issue https://github.com/clojars/clojars-web/issues/801 for it already.

> For existing libraries there isn't a need to change anything AFAIK. I was trying to work out if there was something I could do about the libraries I've already...

Yes, I know.

I guess another alternative is to release `dev.weavejester/hiccup`, but to change the core namespace (say to `weavejester.hiccup`). The advantage would be that I could omit the legacy Hiccup 1 namespaces...

Understood; I guess that means that Hiccup 2 is de facto stable anyway.

I've release Hiccup 2.0.0-RC1. If this turns out to have no issues, I'll release it again as 2.0.0.

`html5` is a macro, and some of the options it takes are necessary to be known at compile-time. In this case, I'd suggest not using the macro, and instead write:...

I don't believe there's any support for this currently. Allowing cljfmt to find config files on the classpath would be useful functionality. An `:extra-configs` or `:include-configs` key might also be...

This library doesn't use Java deserialization, so it shouldn't be directly affected. The Clojure dependency indicates the minimum version the library is compatible with, and is overridden by whatever version...