Maven Repository Type Categorization and Optimization

Summary

Implement Maven-specific upstream categorization to optimize package resolution by routing requests only to appropriate repository types (snapshots vs releases).

Description

Maven repositories typically serve either snapshot versions (development builds) or release versions (stable builds), though some serve both. By categorizing upstreams and routing requests intelligently, we can significantly reduce unnecessary upstream queries and improve performance.

Acceptance Criteria

Repository Type System

• Implement repository type classification: Snapshots Only, Releases Only, Both, Auto-detect
  • Add automatic detection based on repository metadata and URL patterns
  • Allow manual override of auto-detected categorization
  • Default to Both when categorization cannot be determined
  • Support bulk categorization updates for existing upstreams

Performance Optimization

• Route snapshot requests only to appropriate upstreams (Snapshots Only, Both)
  • Route release requests only to appropriate upstreams (Releases Only, Both)
  • Implement fallback to all upstreams if no type-appropriate upstreams available
  • Track and report query reduction metrics

UX/Design Requirements (ideas)

Repository Type Configuration

• Design clear repository type selector with explanatory descriptions:
  • "Snapshots Only" - Development builds ending in -SNAPSHOT
  • "Releases Only" - Stable release versions
  • "Both" - Mixed repository serving all versions
  • "Auto-detect" - Let system determine from repository
  • Add visual preview showing what the system detected vs user selection
  • Include inline help explaining when to use each type
  • Show type mismatch warnings when detected type differs from configured type

Upstream List Enhancements

• Add color-coded type badges (blue=snapshots, green=releases, purple=both)
  • Show detection confidence indicators ("High confidence", "Low confidence", "Manual override")
  • Display last detection scan timestamp and results
  • Add bulk type assignment interface for administrators

Performance Visibility

• Create performance dashboard showing:
  • Query reduction percentage by repository type
  • Average response time improvements
  • Cache hit rate improvements by type
  • Add upstream-specific performance metrics in detail view
  • Show "optimization impact" metrics per virtual registry

Type Detection Interface

• Design "Analyze Repository" button that shows detection results
  • Display detection reasoning (metadata found, URL patterns matched)
  • Allow users to accept, modify, or override detection results
  • Show confidence score and supporting evidence for detection

Error States and Edge Cases

• Handle repositories that fail auto-detection gracefully
  • Show clear messaging for type configuration conflicts
  • Design interface for resolving ambiguous cases
  • Add warnings for repositories that may have changed type over time

Backend Implementation

• Add repository type fields to upstream APIs
  • Implement auto-detection logic and endpoint
  • Add type-aware request routing system
  • Create performance tracking and metrics collection
  • Update caching system to be type-aware

Migration and Compatibility

• Create migration path for existing upstreams (default to "Both")
  • Design bulk analysis tool for administrators to categorize existing upstreams
  • Ensure backward compatibility with existing virtual registries
  • Add admin tools for resolving type conflicts