Decimal points in version numbering cause remotes not to load
In the meta.prop file, having a version number with a decimal point will stop that remote from loading as well as stop all following remotes from being loaded. e.g.:
I've confirmed this by checking the logs in the UR manager. If it's not a bug but actually intended behaviour, feel free to mark it as a suggestion/request. Decimal points are really useful for consistent/semantic versioning. A brief summary:
Given a version number MAJOR.MINOR.PATCH (e.g. 3.8.2), increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
More info here: http://semver.org/
If I remember correctly
meta.versionis a "version code" (i.e. an integer number that is incremented with each new version). However, an invalid version code should of course now cause all following remotes to not load. That definitely sounds like a bug.
Ah okie pokie, that makes sense. If you want to test it for yourself, name a remote folder "A Remote" or something alphabetically first, put in the invalid version number, reload remotes in server then check the logs. Only that remote will have loaded.