Version ranges for dependencies in Maven artifacts break existing builds

[kenwenzel]

We consume the platform bundles via Maven Central. The automatically generated Maven POMs use version ranges to reference dependencies.
An example can be found here:
https://search.maven.org/artifact/org.eclipse.platform/org.eclipse.core.runtime/3.12.0/jar

Those version ranges lead to the behavior that new Maven artifacts are immediately picked up if they become available on Central.
If such an artifact is invalid (as is the case with org.eclipse.platform:org.eclipse.equinox.preferences:jar:3.10.0) then all Maven builds are directly broken that depend on some of the root artifacts:

Failed to collect dependencies at org.eclipse.platform:org.eclipse.e4.ui.workbench.swt:jar:0.16.100 -> 
org.eclipse.platform:org.eclipse.e4.ui.workbench:jar:1.4.0 -> 
org.eclipse.platform:org.eclipse.e4.ui.model.workbench:jar:1.2.0 -> 
org.eclipse.platform:org.eclipse.core.runtime:jar:3.12.0 -> 
org.eclipse.platform:org.eclipse.equinox.preferences:jar:3.10.0 -> 
org.osgi.service:org.osgi.service.prefs:jar:[1.1.0,1.2.0): No versions available for org.osgi.service:org.osgi.service.prefs:jar:[1.1.0,1.2.0) 
within specified range -> [Help 1]

I would suggest that the Maven POMs only reference fixed versions and, if this is possible, the published artifacts are somehow validated before publishing them to Central.

[kenwenzel]

CC @mfriedemann

[akurtakov]

Duplicate of eclipse-equinox/equinox.bundles#54