Skip to content

regression: ScalaMock failing, fails to use Scala-version-specific source directory #434

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

Closed
SethTisue opened this issue Dec 8, 2016 · 3 comments
Assignees

Comments

@SethTisue
Copy link
Member

because scala/scala-dev#252 remains unfixed, sbt doesn't use core/src/main/scala-2.12 and therefore there are compilation failures

example failure log at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1062/consoleFull

@SethTisue SethTisue self-assigned this Dec 8, 2016
@SethTisue
Copy link
Member Author

SethTisue commented Dec 8, 2016

reproducible locally in ScalaMock repo with

set resolvers += "nightlies" at "https://scala-ci.typesafe.com/artifactory/scala-release-temp/"
set every scalaBinaryVersion := "2.12.2-c71e41e-nightly"
scalamock-core/compile

@SethTisue
Copy link
Member Author

ScalaMock:master...origin/master> show scalamock-core/unmanagedSourceDirectories
[info] * /Users/tisue/scalamock/core/src/main/scala-2.12.2-c71e41e-nightly
[info] * /Users/tisue/scalamock/core/src/main/scala
[info] * /Users/tisue/scalamock/core/src/main/java

this suggests a workaround where we simply use extra.commands to do set unmanagedSourceDirectories ...

SethTisue added a commit to SethTisue/community-build that referenced this issue Dec 8, 2016
@SethTisue
Copy link
Member Author

I'm fixing in #433

SethTisue added a commit to SethTisue/community-build that referenced this issue Dec 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant