Migrate from Gradle Enterprise Maven extension to Develocity plugin

What problem are you trying to solve?

https://docs.gradle.com/enterprise/maven-extension/legacy/#develocity_migration

Starting with version 1.21, the extension is available under the “Develocity” brand. Please see the Develocity Maven Extension User Manual for the current documentation. Several APIs, system properties and configuration files have been deprecated with the rebranding and will be removed in the next major version. Therefore, please consider migrating to the new APIs where applicable to minimize the amount of necessary changes when updating to the next major version.

Start by updating the extension’s version to 1.21 and changing the artifact ID to develocity-maven-extension, then rename gradle-enterprise.xml to develocity.xml and update your .gitignore accordingly. If you are using the common-custom-user-data-maven-extension, update the extension’s version to 2.0 After running a goal like ./mvnw test you will be informed about the usage of the deprecated APIs:

Most of the violations can be fixed by replacing references of gradleEnterprise with develocity. Some APIs have been replaced by more descriptive and idiomatic alternatives. In this example, those APIs are goalInputFiles and publish. See Breaking API changes section for this and other examples. After these changes, your extensions.xml and develocity.xml should look like the following:

Locate the Maven extension configuration, gradle-enterprise.xml, develocity.xml, .gitignore, and extensions.xml mentioned in the issue. Start by updating the extension and common-custom-user-data-maven-extension versions, then run ./mvnw test to identify deprecated APIs. Done means the configuration uses the Develocity names and no deprecated API usage remains.