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
Transformation fails in project that depends on itself #13353
Comments
Yeah, I would expend the self-dependency to either be dropped automatically or cause an error. |
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to to let know so we can reopen the issue. Please try to provide steps to reproduce, a quick explanation of your use case or a high-quality pull request. |
I have a project that contains an implementation dependency to itself through a binary dependency. The
preferProjectModules
resolution strategy is then used to replace the dependency with a project dependency to look like this:Applying a transformation in this configuration in a clean build crashes, since the transformation is applied to the output artifact of the project itself which, of course, doesn't exist:
In order to repro, use the repo from #13329 (shared with @ljacomet, @melix and @jjohannes), pull to the latest master, and run:
Environment: Gradle 6.5
Build scan: https://scans.gradle.com/s/rogy6bluv22gg
The text was updated successfully, but these errors were encountered: