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
Use the file resolver in LazyPublishArtifact #18715
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't look like a bad change if it makes things more consistent, but it looks like there are some plugins relying on internal APIs that are busted by this: https://builds.gradle.org/viewLog.html?buildId=46767711&
The Play plugin we might be able to fix to avoid using internal APIs (we control it), but the Nebula and Spring plugins look more worrying.
c80ffe9
to
5fff09b
Compare
8e13524
to
804791e
Compare
...ency-management/src/main/java/org/gradle/api/internal/artifacts/dsl/LazyPublishArtifact.java
Outdated
Show resolved
Hide resolved
subprojects/plugins/src/main/java/org/gradle/api/plugins/internal/JvmPluginsHelper.java
Outdated
Show resolved
Hide resolved
This gives us many of these conversions for free, reducing duplicated code. This also fixes #15711.
51dde6a
to
8a32350
Compare
OK, I've already triggered a build for you. |
Pre-tested commit build failed. |
@bot-gradle test and merge |
OK, I've already triggered a build for you. |
This gives us many of these conversions for free, reducing duplicated code. This also fixes #15711.
The bulk of the change is
LazyPublishArtifact.java
, everything else is dependency injection or test fixing.