slachiewicz opened a new pull request, #2280: URL: https://github.com/apache/maven-resolver/pull/2280
Downstream projects moving from Resolver 1.9.x to 2.x had the deprecation Javadoc and a page that still called 2.x "upcoming" to go on. This rewrites the Upgrading Resolver page as a step-by-step guide and fills the `@deprecated` tags that named no replacement. The page now covers what a consumer project actually hits, in order: what 1.9.x deprecates and 2.x removes, bootstrapping without `ServiceLocator` through the two supplier modules, the `File` to `Path` renames, the Util helpers, module coordinates, the configuration keys that moved to `aether.transport.*` and `aether.lrm.*`, and the changed defaults. The key table marks which old keys 2.x still reads (`userAgent`, `smartChecksums`, `checksums.algorithms`, `enhancedLocalRepository.*`, `syncContext.named.time`); the others are ignored silently. The plugin page gains the Maven to Resolver version table and the rules for a plugin that runs in both Maven 3.9 and Maven 4. Three statements of the old page are gone because they do not hold on the 2.x line: `ArtifactProperties`, `DefaultArtifactType` and the `DependencyFilterUtils` class path filters are not deprecated, and dependency scopes are not removed but delegated to `ScopeManager`. Code changes are Javadoc only. The util `ScopeDependencySelector` and `OptionalDependencySelector` pointed at an internal package; the `spi.locator` shims in `supplier-mvn3`, `DefaultVersionFilterContext#set`, the `NamedLockFactoryAdapter` time constants and the `File` helpers in `TestFileUtils` named no replacement; one `@Deprecated` sat before its Javadoc comment. Verified: `mvn -N site` renders the page with the three pre-existing heading anchors unchanged (`Upgrading_from_1.x_to_2.x`, `Session_handling_changes`, `Consumer_Project_Changes_.28if_more_needed.29`); `javadoc:javadoc` and `spotless:check` on the four touched modules pass. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
