Skip to content

kotlin-stdlib version conflicts downstream #274

Open
@andykruth-ii

Description

@andykruth-ii

Including some dependencies downstream cause a 1.2.X version of kotlin-stdlib and a 1.3.X version of kotlin-stdlib-common to be pulled in which causes version clash issues at runtime (NoSuchMethodError's).

Ex.

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-dependencies</artifactId>
            <version>2.1.1.RELEASE</version>
            <scope>import</scope>
            <type>pom</type>
        </dependency>
        <dependency>
            <groupId>com.expediagroup.streamplatform</groupId>
            <artifactId>stream-registry-state-graphql-sender</artifactId>
            <version>0.16.0</version>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependencies>
    <dependency>
        <groupId>com.expediagroup.streamplatform</groupId>
        <artifactId>stream-registry-state-graphql-sender</artifactId>
    </dependency>
</dependencies>

This resolves to:

  • kotlin-stdlib : 1.2.71
  • kotlin-stdlib-common : 1.3.72

Proposed solution is to solidify kotlin-stdlib and kotlin-stdlib-common dependency versions in graphql-sender. Can also take this opportunity to update the kotlin-stdlib dependency in the top level pom.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions