Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sbt-sonatype race condition between guardrail-maven-plugin #31

Closed
blast-hardcheese opened this issue Nov 3, 2019 · 3 comments
Closed

sbt-sonatype race condition between guardrail-maven-plugin #31

blast-hardcheese opened this issue Nov 3, 2019 · 3 comments

Comments

@blast-hardcheese
Copy link
Member

The way sbt-sonatype works currently is publishSigned doesn't maintain which staging repository it just published to.

As a result, if the maven plugin is published at the same time, sbt-guardrail sonatype release fails because sonatypeClose and sonatypeRelease get confused as it doesn't know which one to use.
@blast-hardcheese
Copy link
Member Author

Meant to open against guardrail repo

@blast-hardcheese
Copy link
Member Author

whoops, no I didn't. Misread the title, there's another issue I meant to open against main guardrail repo.

@blast-hardcheese
Copy link
Member Author

I believe this was resolved in the plugin itself

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blast-hardcheese