The GitHub Actions job "Validate GitHub Actions" on grails-core.git/fix/aot-live-instance-beans-8.0.x has succeeded. Run started by GitHub user codeconsole (triggered by codeconsole).
Head commit for run: b22be605696ec37a422bd0a962e70bd4c8657a23 / Scott Murphy Heiberg <[email protected]> Say what the artefacts are read from, and check it holds classes() reads a singleton off the context, and whether the context is there when it is asked was left for the reader to work out. It is, on both paths that ask: the early registration phase sets it on the instance it creates, and the @Bean method is invoked after Spring has applied ApplicationContextAware. It has to be -- the scan beside it resolves resources through the context and did so before any of this was written -- so nothing new is being relied upon. Said in the javadoc now, and covered by a spec on classes() rather than on the method behind it. It reads the bean factory rather than getAutowireCapableBeanFactory(), which refuses a context that has not been refreshed. This is asked while definitions are still being contributed, which is the reason the classes are left as a singleton at all, so asking must not depend on how far the context has got. And a spec for the other end of the same question: a resource locator that inherited nowhere to look still finds a packaged resource, which is what makes emptying the inherited search locations safe rather than merely quiet. Report URL: https://github.com/apache/grails-core/actions/runs/31780243834 With regards, GitHub Actions via GitBox
