You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v1.2.0+, the scapegoat task causes execution of both the compile in the default 'Compile' configuration as well as the compile in the Scapegoat configuration. This was not the behavior in 1.1.1.
This can be seen because it fills in the target\scala-2.13\classes directory when it shouldn't.
Fixing this would ensure the scapegoat task doesn't unnecessarily compile twice and reduce the wait time for the scapegoat task.
The text was updated successfully, but these errors were encountered:
I've concluded that my variation to use project configuration to deal with the scapegoat compiler plugin (in #159) actually causes Scapegoat / compile to delegate to Compile / compile as well leading to double execution of compilation. I'll probably use the original suggestion to only pollute the ivy artifacts instead.
edit: Ivy Configuration seems to exhibit the same side effect, need to dig more still.
In v1.2.0+, the scapegoat task causes execution of both the compile in the default 'Compile' configuration as well as the compile in the Scapegoat configuration. This was not the behavior in 1.1.1.
This can be seen because it fills in the target\scala-2.13\classes directory when it shouldn't.
Fixing this would ensure the scapegoat task doesn't unnecessarily compile twice and reduce the wait time for the scapegoat task.
The text was updated successfully, but these errors were encountered: