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.

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

Updating to sbt 1.x #11

Merged
merged 17 commits into from
Oct 10, 2017
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,7 @@ object ReleaseEarly {
logger.info(Feedback.logReleaseSonatype(projectName))
// Trick to make sure that 'sonatypeRelease' does not change the name
import Sonatype.{sonatypeRelease => _, sonatypeOpen => _}
val toRun = s";sonatypeOpen $projectName;publishSigned;sonatypeRelease"
val toRun = s";sonatypeOpen $projectName;$projectName/publishSigned;sonatypeRelease"
Copy link
Collaborator Author

@laughedelic laughedelic Oct 9, 2017

Choose a reason for hiding this comment

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

So this was the fix for that CI failure? Another sbt scoping trap...

Copy link
Owner

Choose a reason for hiding this comment

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

Yeah, it was a legit issue... once you go the command way, you need to manually speciify which command you really meant. Glad I found this, it was a real bug.

runCommandAndRemaining(toRun)(state)
()
}
Expand Down