[MRESOLVER-465] Make room for new version scheme implementations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-alpha-7, 2.0.0
• Component/s: Resolver
• Assignee: Tamas Cservenak
• Reporter: Tamas Cservenak
• Created: 17/Jan/24 09:20
• Updated: 17/Jan/24 15:35
• Resolved: 17/Jan/24 15:35

Description

Since eons Resolver had the "generic" scheme implementing the Version, VersionRange and VersionConstraint API interfaces.

Interesting fact: GenericVersionRange and GenericVersionConstraint are NOT tied in any way to GenericVersion implementation, they are happy with plain Version interface as well, they are truly "generic".

This means, that a scheme needs really only to provide Version implementation (currently in form of GenericVersion) and a "factory" for it (currently in a form of GenericVersionScheme).

Refactor a bit, and make room for alternate Version implementations.

Fact: the change can be done in source and binary compatible way, and is enforced by japicmp.

Issue Links

• links to: GitHub Pull Request #407