-
Notifications
You must be signed in to change notification settings - Fork 0
Ability to run as a separate task #1
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
Comments
Thank you for reporting this.
What do you think is better? |
I am used to the separate task approach (e.g. this is how we run |
Probably, it can be done both ways, and the user can choose what is more convenient. |
Sadly, Scala Gradle plugin is written in a such way, that it's very difficult to extend tasks. It seems the only way to go is to copy-paste a huge chunk of code. |
Uh oh!
There was an error while loading. Please reload this page.
As far as I understand currently when using the plugin Scapegoat is being run together with all the compile tasks.
It'd be useful to be able to have it defined as a separate task and trigger it separately, e.g.
./gradlew scapegoat
.The real-life use-case for this is dealing with large code base which has tons of violations and gradually introducing Scapegoat to clean up some mess.
The text was updated successfully, but these errors were encountered: