Stuart Sierra's dependency library, but I started over using deps-new
to get a feel for the new deps thing.
deps-new
generates apom.xml
but this appears to be worthless - just delete itbb/jar
generates a POM which is missing a lot of information. See template-pom for more info.- I'm unsure how to sign - maybe I apply the configuration in
deps-deploy
to theopts
provided to thedeploy
call?
- Create a
template/pom.xml
- Reference in
build.clj
ci
function eg(assoc opts :src-pom "template/pom.xml")
.
Lots of caveats
- The template file requires the schema info on the
project
tag, otherwise the generated POM is unusable. - When using the template file, clojars requires
modelVersion
to be in the template. Otherwisebb/jar
doesn't know which version to specify. bb/jar
does not generatedescription
,url
, orscm
... all of which are necessary to flesh out the clojars webview. They must be included in the template.- However you structure the version string, be sure to check
<scm><tag>xxx</tag></scm>
in the generated POM file. This is how you need to tag the release in github. If you don't do this, cljdoc won't work.