This message was deleted.
# releases
s
This message was deleted.
it seems, however, that the
checkstyleMain
task is eventually created, but later
this breaks scripts which use either:
Copy code
checkstyleMain.enabled = false
or
Copy code
tasks.named("checkstyleMain") {
    enabled = false
}
has ordering of plugin execution changed in 8? If so that's a major unexpected change
g
I'm not aware of anything expected that would cause this. The task should just get created when the sourceSet is created (which is how it has worked for a while). I suspect there's something weird going on, like the sourceSet is getting created later now or something. I was trying to follow the trail of plugin applications in the micronaut build, but I kind of got lost (it's not clear where I might find the "io.micronaut.build.internal.common" plugin). Is this something that's reproducible in a simpler build? If not, can you point me to where I might find that plugin?
m
Hi Gary! And a Happy New Year to you 🙂 Our build plugins live in this repo: https://github.com/micronaut-projects/micronaut-build
👋 1
g
So, looking at this, it makes sense to me why this would fail - you're [applying the checkstyle plugin in an afterEvaluate](https://github.com/micronaut-projects/micronaut-build/blob/e448cc10d8e21898e0686787e2774db3e250b964/src/main/java/io/micronaut/build/MicronautQualityChecksParticipantPlugin.java#L26). So, any reference to the checkstyle task in the build script should fail. What's not clear is why this ever worked. Looking at another (random) build, we see that checkstyle is being [pulled in by io.spring.nohttp](https://ge.micronaut.io/s/z6s3sid7r2sko/performance/configuration?details=code-unit-[…]hmarks&openScriptsAndPlugins=WyJjb2RlLXVuaXQtY2hlY2tzdHlsZSJd). So that might explain why this worked, but not why it isn't working any more. Knowing that the plugins are coming in from an included build, is it possible that the
io.spring.nohttp
plugin was removed in your local build?
m
oh, that's a good finding, I recently removed the nohttp plugin because it's not compatible with Gradle 8, so it explains! I'm trying to get rid of the
afterEvaluate
everytime I find one, sometimes it's not possible, sotimes it is, let's figure that out!
g
👍 Glad to hear it's not anything more weird/complicated.