goutamadwant commented on issue #10436: URL: https://github.com/apache/maven/issues/10436#issuecomment-5612151390
@gnodet I can work on this. I'd add a `SettingsParser` SPI with a default XML implementation, keeping merging, interpolation, validation, and decryption in `DefaultSettingsBuilder`. One scope question: the bootstrap container reads settings before resolving core extensions. Can the first PR leave that loading sequence unchanged and support parsers already available to the settings-building container? Using a parser from `.mvn/extensions.xml` to read the bootstrap settings would need a separate loading mechanism. I'd cover the XML fallback and a custom parser through integration tests, without adding a YAML dependency to core. -- 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]
