https://bz.apache.org/bugzilla/show_bug.cgi?id=65670

            Bug ID: 65670
           Summary: Dependency convergence issue with org.osgi.core
                    (v4.3.1 and v6.0.0) in POI 5.1.0
           Product: POI
           Version: unspecified
          Hardware: Macintosh
                OS: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: POI Overall
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Dependency convergence issue with org.osgi.core (v4.3.1 and v6.0.0).

On one hand, poi and poi-ooxml-full have log4j as a dependency, which uses
org.osgi.core v4.3.1.
On the other hand, poi-ooxml has commons-compress as a dependency, which uses
org.osgi.core v6.0.0.

Here is maven-enforcer-plugin report:

+-org.apache.poi:poi:jar:5.1.0:compile
  +-org.apache.logging.log4j:log4j-api:jar:2.14.1:compile
    +-org.osgi:org.osgi.core:jar:4.3.1:runtime
and
+-org.apache.poi:poi-ooxml:jar:5.1.0:compile
  +-org.apache.commons:commons-compress:jar:1.21:compile
    +-org.osgi:org.osgi.core:jar:6.0.0:provided
and
+-org.apache.poi:poi-ooxml-full:jar:5.1.0:compile
  +-org.apache.logging.log4j:log4j-core:jar:2.14.1:runtime
    +-org.osgi:org.osgi.core:jar:4.3.1:runtime

As a workaround to get rid of the "maven-enforcer" violation I modify the pom
to:

<dependency>
    <groupId>org.apache.poi</groupId>
    <artifactId>poi</artifactId>
    <version>5.1.0</version>
</dependency>

<dependency>
    <groupId>org.apache.poi</groupId>
    <artifactId>poi-ooxml</artifactId>
    <version>5.1.0</version>
    <exclusions>
        <exclusion>
            <groupId>org.osgi</groupId>
            <artifactId>org.osgi.core</artifactId>
        </exclusion>
    </exclusions>
</dependency>

I don't know what issues this exclusion can produce.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to