Skip to content

How to avoid dependency conflict between user application Dag and JavaSDK itself #66329

Open
Open
How to avoid dependency conflict between user application Dag and JavaSDK itself#66329
Labels
AIP-108: java-sdkChange this to an 'area:' label after AIP acceptance.area:dependenciesIssues related to dependencies problemskind:documentationon holdpriority:lowBug with a simple workaround that would not block a release
@jason810496

Description

@jason810496
jason810496
opened on May 4, 2026

It's likely a long-term issue to discussion, we can reconnect on this one after GA of Java-SDK.

What

Advice from TP in previous JavaSDK Demo:

There might be dependency conflict for JVM for larger organization (their application dependencies conflict with dependencies of Java SDK itself)

Metadata

Metadata

Assignees

No one assigned

    Labels

    AIP-108: java-sdkChange this to an 'area:' label after AIP acceptance.area:dependenciesIssues related to dependencies problemskind:documentationon holdpriority:lowBug with a simple workaround that would not block a release

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    AIP-108: Java Task SDK and the Language Coordinator Layer

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions