Hello list, We have a very simple jar with a @Configuration class to extend Prometheus metrics. It works well on CAS 6.6
After upgrading CAS to 7.1, it's not instantiated anymore. I updated it to use the @AutoConfiguration annotation, and deleted the spring.factories and added the org.springframework.boot.autoconfigure.AutoConfiguration.imports file with the class name. With Spring debug set to true, I can see the class name in the [org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLogger] CONDITIONS EVALUATION REPORT, in the Unconditional Classes section. So it should be instantiated, but it never is, and there are no errors. What can be stopping it from being instantiated? Is there some kind of hardening on CAS part stopping random jars from getting their beans instantiated? -- - Website: https://apereo.github.io/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/236a4498-bb95-4151-87e6-e43b4f2c42b5n%40apereo.org.
