pedestal 2025-07-19

@hlship Very minor thing while trying out 0.8.0-beta2 and moving over to connectors. I see the following logged to my console:

WARNING: io.pedestal.http.servlet/servlet was deprecated in version 0.8.0 and may be removed in a future release
Call stack: ... cljdoc.server.pedestal/create-connector -> io.pedestal.http.jetty/create-connector -> io.pedestal.http.servlet/servlet -> io.pedestal.http.servlet/servlet
But it's not me calling io.pedestal.http.servlet/servlet, is it? It's pedestal. So this warning, as a user of pedestal, is somewhat interesting, but not interesting to me. If you want a repro/issue lemme know.

I see this as well. My code does not reference the deprecated NS either.

The code doesn’t actually know who called it, just that it was called. One possibility is to not truncate the stack trace to show where the ball starting rolling. Another is more sophisticated (and time consuming) analysis when a deprecated function is called. But certainly, your code is using the connector and shouldn’t be penalized about the fact that the connector is built on top of the older code.

You can turn these deprecation warnings off, too.

Thanks for the reply, much appreciated! I already use clj-kondo and eastwood to inform me of usages of deprecated things, so turning off the warnings from pedestal is what I shall do.

https://github.com/pedestal/pedestal/pull/950 Also io.pedestal.http.servlet/servlet should not be deprecated, so the PR fixes that as well.

🙌 1

Coolio! Thanks so much!

@hlship minor doc thing I stumbled on: https://github.com/pedestal/pedestal/blob/master/docs/modules/reference/pages/resources.adoc refers and links to io.pedestal.http.resources but this namespace has moved to https://github.com/pedestal/pedestal/blob/0.8.0-beta-2/service/src/io/pedestal/service/resources.clj. Lemme know if you want an issue raised.

Just pushed the fix.

🎉 1