Skip to content

Publish POM-only artifacts for Jupyter purposes #208

Open
@ileasile

Description

@ileasile

Now you list all the needed artifacts right in the integration. It is convenient, but not efficient enough. It's better to publish artifacts for each spark/scala variation and use only a single dependency in the integration. It will significantly speed up the resolution process (3-6 times). I will improve the resolution of multiple dependencies on our side too.

Activity

Jolanrensen

Jolanrensen commented on Sep 1, 2023

@Jolanrensen
Collaborator

Hmm, that would result in another 20 packages on maven central called org.jetbrains.kotlinx.spark.jupyter-dependencies_x.x.x_2.x. I don't think Sonatype can handle that XD The current 40+ are already an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

        Participants

        @Jolanrensen@ileasile

        Issue actions

          Publish POM-only artifacts for Jupyter purposes · Issue #208 · Kotlin/kotlin-spark-api