apache / apache/maven-resolver
Expose transporter details per protocol
Open
enhancement
- Dominant language
- Java
- Stars
- 152
- Forks
- 160
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
### New feature, improvement proposal
Currently it is impossible to tell in advance which transporter implementation is used for which kind of (remote) repository resolver/upload request. In order to ease debugging, this should be exposed via API (without the need for having a concrete RemoteRepository).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how transporter implementations are selected for remote repository resolver and upload requests. Determine an API shape that exposes the transporter per protocol without requiring a concrete RemoteRepository; done means callers can inspect those mappings for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100