Am 09/24/16 um 17:33 schrieb Karl Heinz Marbaise: > Hi Hervé, > So I have marked the class as deprecated... > > But it implements an interface: > > public interface ArtifactVersion > extends Comparable<ArtifactVersion> > > which should be marked as deprecated as well in consequence of the > previous step (my opinion ?) WDYT ? > > > So one more question: > > What about moving DefaultArtifactVersion to maven-compat module...and > replace it with a better implementation ? > > > What might be done is to create an enhanced version of the interface and > make a better implemtation (based on ComparableVersion or make same > getters to get the parsed information from it...)
Maybe delegate to <https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=tree;f=maven-resolver-api/src/main/java/org/eclipse/aether/version;h=a8a6d1f035ef520b8c4ea748bac8a70dbe795fb3;hb=HEAD> <https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=tree;f=maven-resolver-util/src/main/java/org/eclipse/aether/util/version;h=66770e368eb28041378f80c3f315276737b43597;hb=HEAD> to keep things consistent. There should only be one versioning implementation used consistently everywhere. The resolver already handles version ranges differently than the Maven artifact API, for example. We already have two different artifact APIs and need to keep these consistent. <https://git-wip-us.apache.org/repos/asf?p=maven-resolver.git;a=tree;f=maven-resolver-api/src/main/java/org/eclipse/aether/artifact;h=b58a84696390967f22731dd2e1f918b1af44a244;hb=HEAD> Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
