Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update sbt to 1.3.0 #237

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
Philippus merged 2 commits into scala:1.2.x from scala-steward:update/sbt-1.3.0
Sep 10, 2019
Merged

Update sbt to 1.3.0 #237

Philippus merged 2 commits into scala:1.2.x from scala-steward:update/sbt-1.3.0
Sep 10, 2019

Conversation

Copy link
Contributor

@scala-steward scala-steward commented Sep 7, 2019

Updates org.scala-sbt:sbt from 1.2.8 to 1.3.0.

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.

Have a fantastic day writing Scala!

Ignore future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: semver-minor

@SethTisue SethTisue self-assigned this Sep 7, 2019
Copy link
Member

the 2.11 jobs are failing, apparently because of some kind of crosstalk between classpaths during Scaladoc generation:

[error] java.lang.NoClassDefFoundError: scala/util/parsing/json/JSONArray

in 2.11, scala-compiler still depended on scala-parser-combinators, that isn't true from 2.12 on

@ashawley did we run into something comparable over in scala-xml?

@eed3si9n is it obvious to you why this might be different in 1.3.0?

@SethTisue SethTisue removed their assignment Sep 9, 2019
Copy link
Member

Philippus commented Sep 9, 2019
edited
Loading

is this a repeat/variant of #197 ?

Copy link
Member

Philippus commented Sep 9, 2019
edited
Loading

I think this is the same issue as sbt/sbt#4995.
The workaround mention in sbt/sbt#4995 (comment) works locally for me as well (adding ThisBuild / useCoursier := false).

Copy link
Member

since only two repos in the world are affected, I think it's fine to go ahead with that workaround. want to do the honors? (you can push additional commits onto scala-steward's branches)

Philippus reacted with thumbs up emoji

Copy link
Member

I suppose the workaround could be limited to the 2.11 case only, and we leave coursier enabled for the other Scala versions? but whatevs, nbd either way

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

@SethTisue SethTisue SethTisue approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /