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

bloop-maven: support per-execution configuration #29

Open
nigredo-tori opened this issue Dec 30, 2021 · 4 comments
Open

bloop-maven: support per-execution configuration #29

nigredo-tori opened this issue Dec 30, 2021 · 4 comments

Comments

@nigredo-tori
Copy link

Here we take scalac options etc. from the //plugin/configuration element in pom.xml. However, Maven has an option to override that configuration on a per-execution basis. This can be used, for example, to set different scalac options for compile and testCompile goals.

@tgodzik
Copy link
Contributor

tgodzik commented Dec 30, 2021

Thanks for reporting! Do you have an example of such a project? I would greatly help out figuring out the issue. We can use it for the tests to quickly check if everything is working properly.

@nigredo-tori
Copy link
Author

I don't have an example project right now. I'll try and whip something up, but it'll probably be a couple of days.

@tgodzik
Copy link
Contributor

tgodzik commented Dec 30, 2021

Thanks!

@nigredo-tori
Copy link
Author

nigredo-tori commented Jan 3, 2022

Here's a tiny example. It has kind-projector plugin enabled using per-execution configuration, which Bloop import ignores. As a result, Maven can compile the project just fine, while Bloop fails, and Metals shows a compilation error.

@ckipp01 ckipp01 transferred this issue from scalacenter/bloop Dec 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants