-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curations: version range not working for 4 digit versions #6153
Comments
I believe the better reference is https://ant.apache.org/ivy/history/2.1.0/settings/version-matchers.html. |
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
For this issue, our underlying vdurmont/semver4j library is known to have some (similar) issues. Unfortunately, that library does not seem to be actively maintained anymore. There's a maintained fork / copy at semver4j/semver4j that fixes some of the issues and has a significantly changes API. However, while porting to it I discovered several other issues. TL;DR, don't expect this to get fixed very soon.
That's actually something I would expected to get fixed at all. Such a four-digit version cannot easily be extended to a Semver (like a two-digit version), and people actually expect it to not be accepted. |
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
After further testing another bug hits the stage: For transitive dependencies, curations with prefix matcher version (f.e.g 1.+) doesn't work either: You can test it with:
It has a dependency on:
version matcher has to be removed for the curation to work here:
|
As an unrelated side-note, mappings like these are a bit risky as the page's contents could change any time, mentioning a different license than MIT. I'm playing with #5259 to resolve this. |
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy of the original semver4j library by @vdurmont. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy [1] of the original semver4j library by @vdurmont [2]. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j [2]: https://github.com/vdurmont/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
The new semver4j GitHub organization contains a maintained fork / copy [1] of the original semver4j library by @vdurmont [2]. However, the API changed quite significantly. Catch up with those changes in order to (partly) fix issue #6153. [1]: https://github.com/semver4j/semver4j [2]: https://github.com/vdurmont/semver4j Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
Related: #6922 |
By now we've migrated to semver4j/semver4j, which also had several bug fix releases. Please reopen (and provide a test case) if there is anything left to do. |
Hey,
Concerning curations, it seems that ivy-style version ranges doesn't work for four digit versions like 1.1.1.3.
ivy-style version matcher introduction: https://docs.gradle.org/current/userguide/single_versions.html
Working Solutions
single version 1.1.1.3
NuGet::Xamarin.Android.Arch.Core.Common:1.1.1.3
prefix matcher 1.1.1.+
NuGet::Xamarin.Android.Arch.Core.Common:1.1.1.+
prefix matcher 1.+
NuGet::Xamarin.Android.Arch.Core.Common:1.+
Non-Working Solutions
version range [1.1.1,)
NuGet::Xamarin.Android.Arch.Core.Common:[1.1.1,)
version range [1.1.1.1,)
NuGet::Xamarin.Android.Arch.Core.Common:[1.1.1.1,)
Can you please check that?
The text was updated successfully, but these errors were encountered: