What's the state on optional dependencies? E.g. https://app.circleci.com/pipelines/github/cljdoc/builder/25114/workflows/4c54eb85-a29b-4f23-a9d5-5dd71f0876d5/jobs/41489 fails because some lib is not on the classpath. Shouldn't the analyzer be resilient to this?

Or does cljdoc accept a list of aliases to include, or some command to produce the classpath?

I think the current way to handle this use case is to specify the optional dep as provided in your pom.xml.

> Or does cljdoc accept a list of aliases to include, or some command to produce the classpath? There is currently no feature that supports these.