gnodet opened a new issue, #13528: URL: https://github.com/apache/maven/issues/13528
Part of #13460 — Migrate Maven internals from v3 to v4 API ## Context The `org.apache.maven.configuration` package in `impl/maven-core` contains: **Public API (unused — zero callers in production code):** - `BeanConfigurator` — single-method interface - `BeanConfigurationRequest` / `DefaultBeanConfigurationRequest` - `BeanConfigurationException` - `BeanConfigurationValuePreprocessor` - `BeanConfigurationPathTranslator` / `BasedirBeanConfigurationPathTranslator` **Internal (Plexus-coupled):** - `EnhancedComponentConfigurator` — extends Plexus `BasicComponentConfigurator` - `EnhancedConfigurationConverter` — extends Plexus `ObjectWithFieldsConverter` - `EnhancedConverterLookup` — extends Plexus `DefaultConverterLookup` - `EnhancedCompositeBeanHelper` — record/constructor injection support The internal classes import **37 Plexus types** (`BasicComponentConfigurator`, `ObjectWithFieldsConverter`, `ConverterLookup`, `ClassRealm`, `PlexusConfiguration`, `ExpressionEvaluator`, `Xpp3Dom`, etc.). The package is **not exported** in module-info. ## Usage - `BeanConfigurator` interface: **zero callers** outside its own package - `EnhancedComponentConfigurator`: used in **one place** — `DefaultMavenPluginManager`, which selects `"enhanced"` vs `"basic"` configurator by name for v4 API mojos ## Goal 1. **Drop** the unused `BeanConfigurator` / `BeanConfigurationRequest` public API — no callers, no breakage 2. **Replace** `EnhancedComponentConfigurator` with a v4-native mojo configuration mechanism using Maven's own DI/XML infrastructure instead of Plexus component configurator 3. Removes a significant chunk of Plexus coupling from maven-core ## Dependencies None — self-contained. Can be picked up independently. ## Complexity Low-medium. The main work is writing a replacement mojo configurator that doesn't depend on Plexus internals. _Claude Code on behalf of Guillaume Nodet_ -- 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]
