cljdoc

2024-06-18T20:35:50.864429Z

i released a library today that has a namespace that relies on a dependency that's not declared in the main :deps map because it's up to users to choose to include it themselves and then require the namespace at their discretion. how do i get cljdoc to avoid analyzing the namespace? https://app.circleci.com/pipelines/github/cljdoc/builder/53037/workflows/486f7254-ffd6-40e0-8f98-8dd1e3a822f7/jobs/69412

martinklepsch 2024-06-18T20:42:12.183039Z

the typical recommendation is to ensure that the dependency is in pom.xml with scope=provided

martinklepsch 2024-06-18T20:42:35.196369Z

but it sounds like you might not have control over pom.xml in a sufficient way?

2024-06-18T20:43:31.962079Z

i am using a simple wrapper library around tools.build/build.clj, so i don't have anything custom in there but i could

dvingo 2024-06-18T22:09:10.965759Z

ran into this myself some time ago and added some custom code to update the pom if you want to copy or refer to it https://clojurians.slack.com/archives/C02B5GHQWP4/p1700578586997709?thread_ts=1699976910.226229&cid=C02B5GHQWP4 [insert sarcastic remark complaining about why this isn't part of tools.build (still)]

👍 1
2024-06-18T23:47:18.672299Z

is that covered by :pom-data now?

dvingo 2024-06-25T15:29:18.986299Z

I'm not sure - the issue was that the dependencies generated by tools-build need to be patched after the fact. I'm guessing tools-build will ignore any deps in pom-data but let us know if it works!

👍 1
2024-06-25T15:42:55.460159Z

ah yeah, that wouldn't work with :pom-data. i'll probably use your code, thanks

2024-06-26T20:07:04.791489Z

okay, I ended up just using a :provided alias that i include in the pom/jar generation. thanks for the help, everyone