-
Notifications
You must be signed in to change notification settings - Fork 92
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
Fix circular dependency exclude rule #126
Conversation
needs rebase now. this LGTM otherwise and I would suggest we merge in a few days if there are no objections |
99e5200
to
afeefa0
Compare
afeefa0
to
4f30084
Compare
I don't understand this PR: the title says "Enable test forking", but the patch removes Note that |
@lrytz I agree. This PR is totally confused. That it's enabled in the plugin maybe explains my misunderstanding. I'll rename this PR, and reword the commits. |
3e84847
to
4c3504d
Compare
* build.sbt (libraryDependencies): There's no evidence that SBT supports Ivy's exclude globbing. See Ivy documentation http://ant.apache.org/ivy/history/2.4.0/ivyfile/artifact-exclude.html
4c3504d
to
006afa4
Compare
The fork setting is already removed by #145, so this is only the dependency exclude rule, now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Despite my effort in scala#126, the exclude rule was using the full scala version number, when it should only be the binary version, e.g. 2.12
Seems there's no evidence that SBT supports Ivy's exclude globbing even though it was trying to be used to exclude
scala-xml
fromscala-compiler
as a test dependency. See Ivy documentation http://ant.apache.org/ivy/history/2.4.0/ivyfile/artifact-exclude.htmlThis will revert forking for test in #112.