-
Notifications
You must be signed in to change notification settings - Fork 135
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
Delete baseline-versions (and nebula.dependency-recommender) #1169
Conversation
Generate changelog in
|
@@ -11,7 +11,6 @@ dependencies { | |||
compile 'com.diffplug.spotless:spotless-plugin-gradle' | |||
compile 'com.google.errorprone:error_prone_refaster' | |||
compile 'com.google.guava:guava' | |||
compile 'com.netflix.nebula:nebula-dependency-recommender' | |||
compile 'com.palantir.configurationresolver:gradle-configuration-resolver-plugin' |
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.
if we're queuing up breaks, perhaps we should cut this one too?
Big fan, this has been a long time coming 👍 |
f591cbd
to
6e60788
Compare
Before this PR
To avoid breaking consumers, baseline has bundled nebula.dependency-recommender for a long time, even though we discourage people from using it (as we now recommend GCV).
Here's a recent example of nebula causing people confusion: #1167.
After this PR
==COMMIT_MSG==
The deprecated
com.palantir.baseline-versions
plugin has been deleted, as we recommended using gradle-consistent-versions instead. (Alternatively, you can still manually set up nebula.dependency-recommender).==COMMIT_MSG==
As a follow-up, we might want to excavate a cleanup of the
com.palantir.baseline-versions.disable=true
line from people's gradle.properties.fixes #1131
Possible downsides?