Skip to content

fix: try to fix publishing #619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

SemyonSinchenko
Copy link
Collaborator

@SemyonSinchenko SemyonSinchenko commented Jul 3, 2025

What changes were proposed in this pull request?

TLDR;

  • due to sunset of legacy nexus we should use sbt-ci-release 1.11+
  • starting from 1.11.x there we can't overwrite the namespace (sonatypeProfileName)
  • the only way is to have groupId equal to io.graphframes instead of org.graphframes (!)

See: sbt/sbt-ci-release#385
See: sbt/sbt-ci-release#375
See: https://central.sonatype.org/publish/requirements/#correct-coordinates

etc.

Why are the changes needed?

#618

P.S. I think it won't be hard to migrate (just one line in dependencies), isn't it?
P.P.S. Overall I'm fine to migrate the whole namespace (I mean to change it in the code), but it would so breaking change that maybe it is better to postpone

@SemyonSinchenko SemyonSinchenko self-assigned this Jul 3, 2025
@SemyonSinchenko SemyonSinchenko linked an issue Jul 3, 2025 that may be closed by this pull request
6 tasks
Copy link
Collaborator

@james-willis james-willis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imo it doesnt matter if hte org on the maven import matches the import in source code.

@SemyonSinchenko SemyonSinchenko merged commit 1b5c41e into graphframes:master Jul 3, 2025
5 checks passed
@SemyonSinchenko SemyonSinchenko deleted the 618-publishing-problems branch July 19, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug: publishing is broken
2 participants