arturobernalg commented on PR #13727: URL: https://github.com/apache/maven/pull/13727#issuecomment-6441004641
@slawekjaranowski thanks for the context. I checked how that intent holds up now: - `maven-core`/`maven-embedder` on `maven-3.10.x` don't depend on `maven-shared-utils` at all anymore (grepped both poms, no match). - - `maven-shared-utils`'s own `jansi` dependency is declared `optional`, so it was never pulled in transitively just by depending on `maven-shared-utils` -- a plugin that wants `AnsiMessageBuilder`/`MessageUtils` has always had to declare `org.fusesource.jansi:jansi` itself. So the export's only effect today is on that plugin's own explicit `jansi` declaration, and `DefaultArtifactFilterManager` strips it assuming core provides a replacement -- which it no longer does since #11874. The export can't be helping anyone run `maven-shared-utils`'s jansi-based formatting anymore; it can only break it, exactly as reported in jkube's case. Happy to be shown a path I'm missing, but I don't see one. -- 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]
