Skip to content
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

MavenCentral: Fix parsing of library artefacts #34

Merged
merged 1 commit into from
Jul 25, 2019

Conversation

tindzk
Copy link
Owner

@tindzk tindzk commented Jul 24, 2019

If an organisation contains multiple artefacts with the same prefix
followed by a digit, this digit would be considered as part of the
version:

✗ Could not parse version '8_2.12'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13.0-RC2'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13.0-RC2'. Falling back to comparison by natural ordering...
[...]

These errors were reported to the user when running seed update on
projects that use the scribe-slf4j dependency.

@tindzk tindzk force-pushed the bug/version-ordering branch from adb33fb to cdfba60 Compare July 25, 2019 08:15
If an organisation contains multiple artefacts with the same prefix
followed by a digit, this digit would be considered as part of the
version:

```
✗ Could not parse version '8_2.12'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13.0-RC2'. Falling back to comparison by natural ordering...
✗ Could not parse version '8_2.13.0-RC2'. Falling back to comparison by natural ordering...
[...]
```

These errors were reported to the user when running `seed update` on
projects that use the `scribe-slf4j` dependency.
@tindzk tindzk merged commit ea4c24b into master Jul 25, 2019
@tindzk tindzk deleted the bug/version-ordering branch July 25, 2019 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant