Skip to content

Root publication should serve as an entry point that references all target-specific publications #381

@tomkoptel

Description

@tomkoptel

Hello 👋

I was testing the multiplatform artifact of pubnub-kotlin. I use amper as a build tool. As a consumer of root publication com.pubnub:pubnub-kotlin:11.0.0 I do expect the pubnub-kotlin-11.0.0.module to list all available publications. On practice I had to rely on pubnub-kotlin-api-11.0.0.module as a root publication and I find this experience misleading.

Expected

product:
  type: lib
  platforms: [ jvm, android ]

dependencies:
  - com.pubnub:pubnub-kotlin-api:11.0.0

Actual

product:
  type: lib
  platforms: [ jvm, android ]

dependencies:
  - com.pubnub:pubnub-kotlin-api:11.0.0

dependencies@jvm:
  - com.pubnub:pubnub-kotlin:11.0.0

dependencies@android:
  - com.pubnub:pubnub-kotlin:11.0.0

As can be seen I need declare the GAV of pubnub-kotlin-api.

P.S. The original issue mentioned on Kotlin Slack https://kotlinlang.slack.com/archives/C062WG3A7T8/p1762803465101069

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