-
Notifications
You must be signed in to change notification settings - Fork 19
Jetty code run during compilation #22
Comments
Hi, I think this might be triggered by this, I will change it to be more lazy. (ns qbits.jet.client.ssl
(:import (org.eclipse.jetty.util.ssl SslContextFactory)))
(def ^SslContextFactory insecure-ssl-context-factory
(SslContextFactory. true)) |
This should be fixed by a9f435a |
I ll cut a release shortly (I want to get rid of some reflection that was introduced by a recent PR before). |
Available as [cc.qbits/jet "0.6.6"] Thanks for the report! |
nice! 👍 |
Hmm unfortunately, just tested with the latest and still see the logging initialized message during compile. Possibly another place somewhere that triggers it? |
I think this could be something in clojure itself, I just tried to comment everything and find the source and it seems it's triggered when importing some jetty ns as well. |
I agree, it does seem completely harmless but would be nice to figure out what's causing it. |
When the uberjar is compiled with Jet the following output ends up in the console:
The message comes from jetty as seen here. This indicates that some jetty code is being being run during the compilation step. I didn't notice jet itself calling anything explicitly, so perhaps it's something in jetty config that runs.
It doesn't affect the functionality as the uberjar will still compile, just a bit of a curiosity as it technically shouldn't happen at compile time.
The text was updated successfully, but these errors were encountered: