-
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
Add a normal task with no arguments #68
Comments
Thanks for your input. I agree that we can change things to make this easier, and I think your idea of having a normal input task is a good one, and would cover the bases. Now all we have to do is think of a good name: how about scalastyleTask |
My comment saying that we "first call the compile task" is a bit misleading since we are not really calling it, sbt will figure out the order for us. There is also an unused I went to the sbt docs to go and lookup Defining a sequential task with Def.sequential and low and behold the example is exactly what we want. Keeping in mind that it should be a "raw task" so that users can choose the configuration to use (for reference Provide raw settings and configured settings). As for the name, that is a hard one. I would say that it should probably start with In terms of completeness I would be inclined to do something like:
If I remember this later I'll double check that it works and submit a PR. |
@steinybot this would be really helpful! |
The user guide suggests that to run scalastyle as part of another task you need to add:
There is actually another way which doesn't loose the compiler errors:
The idea here is really simple which is to first call the compile task, then the scalastlye task and finally return the result of the compile task. This is quite verbose and not future proof since it is essentially reimplementing the
scalastyle
input task.It would be far simpler if there was a normal task (not an input task) provided by the plugin.
The text was updated successfully, but these errors were encountered: