Expose transporter details per protocol #1770

Activity

1. kwin

   added

   enhancementNew feature or requestNew feature or request

   on Jan 28, 2026
2. kwin commented on Jan 28, 2026

   

   kwin

   on Jan 28, 2026

   MemberAuthor

   More actions

   Problem right now is that TransporterFactory.newInstance always takes a RemoteRepository to check if it should be used. It fails with an exception if it doesn't support the given repository url. Probably this should be refactored so that a more targeted lookup can be performed (also in

   maven-resolver/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultTransporterProvider.java

   Line 104 in ec52693

   LOGGER.debug("Could not obtain transporter factory for {}", repository, e);

   ).

   Maybe adding another method boolean canHandle(String protocol) (by default always returning true) to TransporterFactory in combination with something like String getDescription() (returning some explanation on which library is used etc). would be reasonable.
3. kwin

   added 3 commits that reference this issue on Jan 28, 2026

   Expose transporter details per protocol

   ...

   This issue will close once commit cd09367 is merged into the 'master' branch.

   cd09367

   Expose transporter details per protocol

   ...

   This issue will close once commit 9079c94 is merged into the 'master' branch.

   9079c94

   Expose transporter details per protocol

   ...

   This issue will close once commit 6233e73 is merged into the 'master' branch.

   6233e73