Invalid version not parsed

[DavidGoodenough]

If you have JavaFx as a dependency you will get (amongst others):-

[info] org.openjfx:javafx-base : 16 -> InvalidVersion(18-ea+1) -> 15.0.1

So it would appear that sbt-updates can not cope with all the version number formats that are allowed by Maven and are in use within the Scala/Java community.

[rtimush]

The problem here was that 16 wasn't considered a valid version because it had too few components. This should be fixed in #244.
I just published 0.6.0, please check if it works for you.

[DavidGoodenough]

I can confirm that with 0.6.0 it no longer says there is an InvalidVersion (if the problem was the 16, why did the message put the InvalidVersion around the 18-ea+1?), but it also no longer thinks that I could upgrade to 18-ea+1, it says they are all up to date.

[rtimush]

Good. The update is not shown because 16 is considered to be a release version and 18-ea+1 to be a pre-release one. sbt-updates doesn't offer such updates. I'm not sure what ea+1 means in this particular case, but if you update to such version once, the future "ea" versions should be offered as potential updates.

[DavidGoodenough]

ea in this case is Early Access, its a sort of pre-release version.