Sorry for the very late reply but we are currently doing some work on the gradle plugin.
I don’t think the plugin is impacted since we don’t define finalizedBy constraints. If users define finalizedBy constraints, the order of execution could change with the upgrade to gradle 7.5 but that’s out of our control. In any case thanks for the heads up.
Thank you for your reply, @dmeneses . No need for the sorry, there actually was a question mark in my post but - as i am sure - you, too, understood that the whole post was more of an informational kind.
Good to hear that the plugin itself is not impacted!
P.S.: Currently i am wondering about two totally out of context things in this post.
a) why does it say “Solved by … in post → #6 <–” when your post was the second visible posting in this thread?!
b) why is your reply marked as an answer, at all? Should it not be decided by the thread opener what is a viable answer?
… just wondering, because i see it as a valid answer, too … (oh but - just in case to give you more time to answer - i will remove the answered-flag only for now … i will re-mark as an answer later. maybe as a christmas present? )
There are sometimes “behind the scenes” discussion/actions between SonarSourcers before responding – or simply notes left for ourself before coming back with a response. It might be interesting feedback for Discourse, which runs this platform.
There’s no internal contest for solved threads, I promise! And, we try and actively discourage internal users from marking their answer as solved, to give the OP more agency and because it triggers the countdown to lock the thread. So… consider this another reminder to SonarSourcers.