Skip to content

Workaround SBT regression to avoid an empty-named JAR entry #8652

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
Merged
merged 1 commit into from
Jan 22, 2020
Merged

Workaround SBT regression to avoid an empty-named JAR entry #8652

merged 1 commit into from
Jan 22, 2020

Conversation

retronym
Copy link
Member

No description provided.

@scala-jenkins scala-jenkins added this to the 2.13.2 milestone Jan 21, 2020
@retronym retronym requested a review from eed3si9n January 21, 2020 23:31
@retronym retronym mentioned this pull request Jan 21, 2020
Merged
@retronym retronym merged commit a2fbeae into scala:2.13.x Jan 22, 2020
@SethTisue SethTisue added the internal not resulting in user-visible changes (build changes, tests, internal cleanups) label Jan 22, 2020
@som-snytt
Copy link
Contributor

Thanks, I just hit this right before I left the office. I wanted to see if -Xlint would affect the scala command under sbt.

@retronym retronym mentioned this pull request Jan 24, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@eed3si9n eed3si9n eed3si9n approved these changes

Assignees
No one assigned
Labels
internal not resulting in user-visible changes (build changes, tests, internal cleanups)
Projects
None yet
Milestone
2.13.2
Development

Successfully merging this pull request may close these issues.
5 participants
@retronym @som-snytt @eed3si9n @SethTisue @scala-jenkins