Skip to content

License concern: GPL-2.0 w/ Classpath Exception via android-retrofuture (azure-communication-calling) #2121

@pyylampi

Description

@pyylampi

License Concern: GPL-2.0 w/ Classpath Exception

Transitive Dependency via android-retrofuture

Artifact: com.azure.android:azure-communication-calling


Summary

We are currently integrating:

com.azure.android:azure-communication-calling

into our Android application.

During the build process, our license compliance checks failed due to
transitive dependencies licensed under GPL-2.0 with Classpath
Exception
.

The issue was detected by the AboutLibraries Gradle plugin,
configured with strict enforcement:

strictMode = StrictMode.FAIL

Our build also defines an explicit allowedLicenses list.
GPL-2.0 (including with Classpath Exception) is not included in our
organization's approved licenses.


Dependency Chain

The following transitive dependency chain was identified:

azure-communication-calling
  └── android-retrofuture
        └── android-retrostreams

Both:

  • android-retrofuture
  • android-retrostreams

are licensed under GPL-2.0 with Classpath Exception, which triggers
our strict license validation failure.


Questions

We would appreciate clarification on the following:

  1. Is the use of android-retrofuture intentional and required?
  2. Are there plans to replace this dependency with one under a more
    permissive license (e.g., Apache 2.0 or MIT)?
  3. Is there official guidance from the Azure SDK team regarding usage
    of this dependency in commercial applications with strict license
    compliance requirements?

Environment Details

  • Artifact: com.azure.android:azure-communication-calling
  • License validation tool: AboutLibraries Gradle plugin
  • Enforcement mode: StrictMode.FAIL

Thank you for your assistance and clarification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions