You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2024/07/01 11:05:00 UTC

[jira] [Closed] (MRESOLVER-570) Remove excessive strictness of OSGi dependency metadata

     [ https://issues.apache.org/jira/browse/MRESOLVER-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet closed MRESOLVER-570.
-------------------------------------
      Assignee: Guillaume Nodet
    Resolution: Fixed

> Remove excessive strictness of OSGi dependency metadata
> -------------------------------------------------------
>
>                 Key: MRESOLVER-570
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-570
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>    Affects Versions: 2.0.0-alpha-11, 1.9.20
>            Reporter: Hannes Wellmann
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 2.0.0, 1.9.21, 2.0.0-beta-1
>
>
> The OSGi dependency metadata in multiple resolver artifacts are stricter than the declared Maven dependency counterparts and should be harmonized.
> For example for the {{maven-resolver-impl}} the dependencies to {{{}Guice{}}}, {{Eclipse Sisu}} and {{javax.inject}} are not marked as optional.
> Furthermore the dependency to the org.slf4j.spi package has a version range of [1.7,2) which mandates a 1.x slf4j-api bundle in the runtime, while the class used from that package is also available in a 2.x version of slf4j-api.
> For all other artifacts the dependency to to javax.inject should be optional as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)