-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot apply 5.0.0 on multi-project build #356
Comments
Can you provide a full stack trace? And ideally your build file. |
I'm unable to provide the build file due to company policies. It is a multi-project build, with quite a few custom convention plugins. The grgit plugin is applied on a subproject and fails when upgrading from 4.1.1 -> 5.0.0. I will try to spend some time on this tomorrow and see if I can narrow down to a reproducible build I can share. Stacktrace:
|
What Gradle version is this? |
7.3
|
Looks like this is a bug in Gradle: gradle/gradle#17559 |
I'm not a fan of the workaround of using |
Thanks for the quick follow-up! Looks like we'll just hold off on the upgrade for now. |
Can this be revisited now that Gradle 7.5 has been released? |
I think Gradle 7.5 hasn't the issue fixed. |
Apologies for the delay getting back to this. I'm trying to reproduce this (see #370) and can't get it to fail. Does anyone have a way to reproduce this error that I can use for a functional test as I work on a solution? |
my guess is that
If you can reproduce, I suspect that adding this to the root of the project will work around the issue: in the root plugins {
id("org.ajoberstar.grgit") apply(false)
} |
Tried reproducing without |
This still hasn't reproduced #356. I also tried creating a separate test project and could not reproduce it. Until someone experiencing this issue reports how to reproduce it'll be closed as invalid.
With the upgrade to grgit 5.0.0 we're no longer able to apply the plugin to our projects:
The text was updated successfully, but these errors were encountered: