[REST API] Created a /search/versions
endpoint
#4726
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows searching for versions across all groups and artifacts. It has two variants:
The latter variant also replaces the old way of figuring out which version of an artifact uses specific content, which was semantically problematic and existed here:
POST /groups/:groupId/artifacts/:artifactId
That operation has been removed. Now if you need to find an artifact version by content you must use the
POST
variant of/search/versions
and includegroupId
andartifactId
filter query params (along with optional sorting and limiting params). It's much more flexible and I think makes a lot more sense semantically.Note that I also renamed
type
properties in the REST API definition toartifactType
since we've done the same for all our IDs. It seems redundant but I think adds clarity.