-
Notifications
You must be signed in to change notification settings - Fork 52
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
scalastyleSources does not include all source directories #47
Comments
Pinging @adrian-wang since this is related to #41. Note that (scalastyleSources in Compile) <++= unmanagedSourceDirectories in Compile But doing the same for the |
Hi @fthomas , did you use
or
? |
I tried all of (scalastyleSources in Test) <++= unmanagedSourceDirectories in Compile,
(scalastyleSources in Test) <++= unmanagedSourceDirectories in Test,
(scalastyleSources in Test) <++= unmanagedSourceDirectories in (Test, compile),
(scalastyleSources in (Test, compile)) <++= unmanagedSourceDirectories in Compile,
(scalastyleSources in (Test, compile)) <++= unmanagedSourceDirectories in Test,
(scalastyleSources in (Test, compile)) <++= unmanagedSourceDirectories in (Test, compile),
(scalastyleSources in (Test, scalastyle)) <++= unmanagedSourceDirectories in Compile,
(scalastyleSources in (Test, scalastyle)) <++= unmanagedSourceDirectories in Test,
(scalastyleSources in (Test, scalastyle)) <++= unmanagedSourceDirectories in (Test, compile), but none of those had the desired effect. In the sbt console |
This is unreasonable... |
Indeed. Is there anything I could do to "debug" this? |
This contains a workaround for scalastyle/scalastyle-sbt-plugin#47
One way we worked around this: scalastyleSources in Compile <++= unmanagedSourceDirectories in Test, This means that running |
Scalastyle is now an AutoPlugin, which may have changed behaviour slightly. Could you recheck this and see if there is still a problem, using 0.9.0-SNAPSHOT please? |
@matthewfarwell I tried 0.9.0-SNAPSHOT but
|
I don't understand the problem. I can do the following (using 0.9.0-SNAPSHOT, but as far as I'm aware this behaviour hasn't changed). Add two directories and single file to scalastyleSources: build.sbt:
Use master scalastyle: project/plugins.sbt:
Make sure the files exist:
And scalastyle processes in the output:
|
@fthomas @adrian-wang Could you see if the behaviour has changed between 0.8.0 and 0.9.0, and if not, please tell me what the problem is, if indeed there is one. Thanks. |
@matthewfarwell The problem still exists in 0.9.0.
instead of all relevant source directories for this project:
Since all my sources are in The problem is not that I cannot change BTW, I had similar issues with other plugins: |
Can you try this with the snapshot and see if it works please? |
Just tried 0.10.0-SNAPSHOT and it picks up all my source directories. Thanks @matthewfarwell! |
This version is compatible with sbt 1.0.0 and allows to get rid of a workaround for scalastyle/scalastyle-sbt-plugin#47. It also complained about new issues which I've ignored for now. The same issues already have been silenced in other places of the library.
This the latest version, and the first one supporting sbt 1.0. Moreover, it now takes "shared" source directories into account by default, i.e., all `unmanagedSourceDirectories`. See the issue scalastyle/scalastyle-sbt-plugin#47. Therefore, we remove the workaround we had for that issue.
This the latest version, and the first one supporting sbt 1.0. Moreover, it now takes "shared" source directories into account by default, i.e., all `unmanagedSourceDirectories`. See the issue scalastyle/scalastyle-sbt-plugin#47. Therefore, we remove the workaround we had for that issue.
In one of my projects Scalastyle 0.8.0 does not inspect all source files. The project is a JVM/JS cross project and has its sources in different directories (
shared/src/main/scala
,jvm/src/main/scala-2.10
,jvm/src/main/scala-2.11
, etc.). and it seems that Scalastyle only inspect files injvm/src/main/scala
becausescalastyleSources
only contains this directory:I suspect
scalastyleSources
should by default instead contain the same directories assourceDirectories
(orunmanagedSourceDirectories
):Btw, the same problem exists in Cats and circe.
The text was updated successfully, but these errors were encountered: