Fixed some Eclipse dependencies version to avoid issues with latest releases #1502
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The builds are failing from yesterday with the message:
The cause is the latest release (v 3.10.0) published yesterday for org.eclipse.platform:org.eclipse.equinox.preferences [1]: in the pom.xml file it declares this dependency:
but this dependency doesn't exist in any public Maven repository (at the comment's date, 2022-06-15).
The "closest" Maven artifact to this one seems to be
org.osgi:org.osgi.service.prefs
(i.e. without.service
in the groupId) which is available, with the expected versions [2].The solution is all about avoiding
org.eclipse.platform:org.eclipse.equinox.preferences:3.10.0
artifact from being used, forcing the previous release (i.e.3.9.100
) to be used instead.[1] https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.equinox.preferences/3.10.0/
[2] https://repo1.maven.org/maven2/org/osgi/org.osgi.service.prefs/