-
Notifications
You must be signed in to change notification settings - Fork 42
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
Android AmbiguousConfigurationSelectionException with Gradle 4.9 and local dependencies #143
Comments
@martofeld Have you tried the dependency lock built into Gradle? |
@sghill It is not our intention to migrate from this plugin since we have a great deal of scripts depending on how nebula works. However, as a side note, Gradle mentions you and mentions a migration guide which I am yet to find. Do you think you could point me in the right direction? |
We don't have a formal migration guide. @OdysseusLives do you have any insight for this? perhaps share some notes around the migration task that is not included? |
I'll update the project with a migration guide, based off of the release notes for these two versions: https://github.com/nebula-plugins/gradle-dependency-lock-plugin/releases/tag/v7.3.1 details setting a system property, using the task https://github.com/nebula-plugins/gradle-dependency-lock-plugin/releases/tag/v7.6.3 details locking additional configurations to lock, via a property |
This is now available in the Wiki at https://github.com/nebula-plugins/gradle-dependency-lock-plugin/wiki/Usage-With-Core-Gradle-Locks |
After migrating to Gradle 4.9 I started getting the issue I mentioned above.
Environment:
Gradle Version: 4.9 and 4.8
Nebula Version: 6.0.0
Android Gradle Plugin: 3.1.0
The issue occurs when I have modules with dependencies to other local modules.
My
build.gradle
is:I have also tried using implementation and still got the same issue.
Let me know if you need any more information
The full stacktrace is:
The text was updated successfully, but these errors were encountered: