Repo using tools fail to work correctly when passed a partial version number

[quintesse]

For example, when you type ceylon run foo/1.0 while the real number is 1.0.0 it will still work. This is not really correct. But worse is that when there are several matching versions, let's say 1.0.0 and 1.0.1 the tool will just choose whatever came first in the list.

[alesj]

Who's doing this partial matching?

On Sep 22, 2014, at 21:37, Tako Schotanus notifications@github.com wrote:

For example, when you type ceylon run foo/1.0 while the real number is 1.0.0 it will still work. This is not really correct. But worse is that when there are several matching versions, let's say 1.0.0 and 1.0.1 the tool will just choose whatever came first in the list.

—
Reply to this email directly or view it on GitHub.

[quintesse]

It's using the query API for that. So it's not a problem with the CMR API, don't worry ;)
Just wrong heuristics for the code that tries to provide helpful suggestions.