Just released antq ver 0.12.0, Tool to point out your outdated dependencies.
https://github.com/liquidz/antq
- Support detecting dependencies which has unverified group name (e.g. seancorfield/next.jdbc
-> com.github.seancorfield/next.jdbc
)
- Support detecting versions in 3rd-party GitHub Actions such as https://github.com/DeLaGuardo/setup-clj-kondo
- Changed GroupId to "com.github.liquidz" which is verified by clojars.
Thank you! I was looking at your tool recently with @lee and we wondered how you manage to package gitlibs (like rewrite-clj at the time) to clojars?
Good to see you moved to the clojars alpha now! https://github.com/liquidz/antq/commit/4a248e3be52c7fc9e6a0f5435d06a560a1721bd2
oh awesome, another rewrite-clj v1 user!
@borkdude I'm not sure if this answers your question, but I'm just deploying the JAR created by depstar.
@lee Thanks for your great work!
@seancorfield Does depstar automatically include sources of gitlibs in a jar?
if you inspect ~/.m2/repository/antq/antq/0.11.2/antq-0.11.2.jar
you will see rewrite_cljc
sources in there which were from a gitlib
@borkdude Yes, because :local/root
and :git/url
on the classpath look just like :paths
so they are all treated as “source” code for the JAR. Folks building JAR files with such dependencies should probably use :exclude
to ensure such things don’t leak into your libraries.
That’s mentioned in the README but only under AOT compilation at the moment: “(which normally corresponds to your own project’s source files, but will also include :local/root dependencies and :git/url dependencies, since those show up as directories on the classpath)”
https://github.com/seancorfield/depstar/issues/73 so I’ll remember to make that clearer.