You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #394: would it make sense to have an option to only include the latest version of found dependency? Does Maven API support that? That way number of results can be drastically reduced and usability would increase a lot. For example, a class might exist in multiple versions of a dependency, starting from 1.0, hence the search would return all those hundreds of results per single dependency. But if there was a flag to tell "I care only about the latest" - that would be always one per dependency and the list would be much shorter. Worst case, if Maven doesn't support that - results can be requested in chunks (known to not cause this issue for Maven), then arranged by name and version and then latest versions returned. Considering Maven naming convention, this should be doable. I might even try to contribute if Maven does not support that :)
The text was updated successfully, but these errors were encountered:
As mentioned in #394: would it make sense to have an option to only include the latest version of found dependency? Does Maven API support that? That way number of results can be drastically reduced and usability would increase a lot. For example, a class might exist in multiple versions of a dependency, starting from 1.0, hence the search would return all those hundreds of results per single dependency. But if there was a flag to tell "I care only about the latest" - that would be always one per dependency and the list would be much shorter. Worst case, if Maven doesn't support that - results can be requested in chunks (known to not cause this issue for Maven), then arranged by name and version and then latest versions returned. Considering Maven naming convention, this should be doable. I might even try to contribute if Maven does not support that :)
The text was updated successfully, but these errors were encountered: