Hannes Wellmann created MRESOLVER-571:
-----------------------------------------
Summary: Import o.e.aether packages with the exact same version in
OSGi metadata
Key: MRESOLVER-571
URL: https://issues.apache.org/jira/browse/MRESOLVER-571
Project: Maven Resolver
Issue Type: New Feature
Components: Resolver
Affects Versions: 1.9.20, 2.0.0-alpha-11
Reporter: Hannes Wellmann
The documentation states that only maven-resolver artifacts of the exact same
version should be used together:
* [https://maven.apache.org/resolver/api-compatibility.html#outside-of-maven]
*
[https://maven.apache.org/resolver/third-party-integrations.html#maven-resolver-supplier]
But currently the OSGi metadata declare version ranges for imported packages up
until (excluding) the next major version:
{{org.eclipse.aether;version="[1.9,2)"}}
My suggestion is to reflect the requirement for a strict version alignment in
the OSGi metadata and change the Package-Imports to (for example for the next
1.9.21 version):
{{org.eclipse.aether;version="[1.9.21,1.9.21]"}}
{{Of course this would make it impossible (without nasty tricks/out of the box)
to break that (strong) recommendation in OSGi runtimes if unexpected
circumstances would require it.}}
{{I'm currently working on providing a PR for the }}1.9.x{{ and }}master/2.x{{
branch}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
