30438

Comment From: wilkinsona

Thanks for the proposal. Unfortunately, I don't think this is the right way to approach this.

As proposed here, the ordering check will be performed once each project has been evaluated. In a Gradle build, work like this should not be performed until the build's execution phase. To occur in this phase, the check should be implemented as a task. It should perhaps be a SourceTask subclass that's configured to include the META-INF/spring-configuration-metadata.json file. Implemented as a task with appropriate inputs and outputs, the ordering check will then be performed in the correct phase and its execution can be avoided through Gradle's up-to-date checking when the file's contents haven't changed.