Konrad Windszus created MRESOLVER-598: -----------------------------------------
Summary: Improve javadoc around version ranges Key: MRESOLVER-598 URL: https://issues.apache.org/jira/browse/MRESOLVER-598 Project: Maven Resolver Issue Type: Improvement Components: Resolver Affects Versions: 2.0.1 Reporter: Konrad Windszus Currently the javadoc at https://github.com/apache/maven-resolver/blob/362a43675f01b8bb3d85d7b0ff76a21d57de6fee/maven-resolver-api/src/main/java/org/eclipse/aether/RepositorySystem.java#L88C24-L88C43 is not clear how the actual version range is being passed to the VersionRangeRequest. Only when looking at the [example|https://github.com/apache/maven-resolver/blob/362a43675f01b8bb3d85d7b0ff76a21d57de6fee/maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples/FindNewestVersion.java#L46 ] it became clear that the bound {{Artifact}} supports version ranges as well. However none of the javadoc of https://github.com/apache/maven-resolver/blob/master/maven-resolver-api/src/main/java/org/eclipse/aether/artifact/Artifact.java#L57 clarifies that version ranges are supported. Also the format of the version range is never explained (I understood this is depending on the underlying provider). -- This message was sent by Atlassian Jira (v8.20.10#820010)