matrei opened a new pull request, #16325:
URL: https://github.com/apache/grails-core/pull/16325
The task-based wiring that 9a529d1996 replaced with a doFirst declared
runtimeClasspath as an input of the generator task, so any task whose output
reached the runtime classpath became a transitive dependency of compileGroovy.
A post-compile step that feeds the runtime classpath, such as asset-pipeline
output or the exploded plugin directory, then closed a cycle. That is the
concern raised on #16114.
The generator introduced there takes its script from grails { } state and
declares no classpath input, so that edge no longer exists. This test recreates
the scenario: a task that runs after classes and puts its output on the runtime
classpath via runtimeOnly files(task). It asserts the generator does not depend
on that task, and that compileGroovy and the producer schedule together without
a cycle.
--
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]
