cstamas commented on PR #406: URL: https://github.com/apache/maven-resolver/pull/406#issuecomment-1893909638
@dmlloyd General remarks: * let's put aside `maven-artifact` (is to be killed off in Maven4, or around). As we know, currently Maven _does suffer_ from existence of these "parallel worlds" (two version parsing and sorting implementation, generally in par, but only "generally"). Goal is to stop doing this, and have _one golden implementation_ that does everything correctly. Current situation is a maintenance nightmare. Hence, let's focus on `maven-resolver-util` versions only. * I tend to NOT modify existing UTs, not to redefine or introduce breaking change needed to touch existing UTs, as that would lead to (most probable) breakage in versions already out there in the wild. * On the other hand, Maven4 is now prepared to support "alternate" version schemes, as somewhat explained in the issue https://issues.apache.org/jira/browse/MNG-7951. The goal would be to have multiple Version implementations (those of Resolver' Version interface), maybe like "legacy" (that implements `maven-artifact` one with all of it's known flaws), then "generic" (this one), and probably in future new ones as well ("semver", "maven4" or whatever improved ones). Still, while doing these, we need to keep eye on interoperability as well, as switching to totally new scheme may really be possibly only in some isolated environment (ie. org that uses ONLY deps with in-org defined versioning). -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
