All internal components are renamed to Develocity #678
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates all internal references from Gradle Enterprise to Develocity.
Much of this is just a simple rename of
ge
andgradle enterprise
todevelocity
, but there were a few occurrences where this wasn't the case. I have outlined any noteworthy and exceptional cases below:configure-gradle-enterprise-maven-extension
toconfigure-develocity-maven-extension
(it still configures both)configure-develocity-maven-extension
had their prefixes updated fromcom.gradle.enterprise.build-validation
todevelocity.build-validation
gradle.enterprise.url
andgradle.enterprise.allowUntrustedServer
as these must remain for as long as we support using the GE Maven extension with the scriptsGradle.md
orMaven.md
has been updated fromhttps://github.com/gradle/gradle-enterprise-build-validation-scripts/blob
to the special short form redirecthttps://gradle.com/bvs
What remains are things that cannot yet be updated. This primarily includes all references to the repository, Gradle Enterprise distributions, bundled GE extension.