Skip to content
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

Regression: scapegoat task is triggering default Compile task #190

Closed
crt-31 opened this issue Oct 2, 2024 · 1 comment · Fixed by #194
Closed

Regression: scapegoat task is triggering default Compile task #190

crt-31 opened this issue Oct 2, 2024 · 1 comment · Fixed by #194
Labels
bug Considered a fault in the plugin

Comments

@crt-31
Copy link

crt-31 commented Oct 2, 2024

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.

@Johnnei Johnnei added the bug Considered a fault in the plugin label Oct 6, 2024
@Johnnei
Copy link
Collaborator

Johnnei commented Oct 9, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Considered a fault in the plugin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants