codeconsole commented on PR #16114: URL: https://github.com/apache/grails-core/pull/16114#issuecomment-5591096750
@jdaugherty I understand the concern about reintroducing task-ordering failures. I should have followed up with you to establish whether the change covered your actual build wiring before this was merged. My [earlier explanation](https://github.com/apache/grails-core/pull/16114#issuecomment-5289016409) addressed the runtime-classpath dependency in the old implementation: the merged generator no longer reads either classpath. That addresses that particular dependency, but does not settle every ordering case you described. I have now reproduced a narrower case in an execution-level test: a build that assigns a plain `configurationScript` file and separately adds its producing task to `compileGroovy.dependsOn` does not order that producer before Grails prepares the combined script. Requesting script preparation first exposes the missing edge and fails because the file does not yet exist. Wiring `configurationScriptFile` to the producing task's output provider makes the same task request compile and run successfully, including after the generated script changes. I'm preparing a follow-up with that regression test and upgrade documentation for the provider wiring. It keeps the generator independent of unrelated compilation prerequisites; copying all of those dependencies could introduce cycles. Returning to the old `doFirst` assignment would also restore the finalized-property failure on Gradle 9.7. Could you share the actual task registration and `compileGroovy` wiring from the affected build, including whether the prerequisite writes the compiler script, changes its contents, or only supplies source/classpath entries? That will let us check your specific case rather than assume the reproduced one is the same. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
