hi all, not sure if this the right channel, but facing and odd behaviour in 2.9.0rc1 when using global scalac plugins, in particular with

kind-projector

. Seeing the error

Missing required plugin: kind-projector

when trying to compile some files, but adding the the

-Xplugin-list

argument to

scalac.args

in

pants.toml

seems to fix it (or at least makes it go away). Funny thing is that we also use the

better-monadic-for

scalac plugin and we never see any error related to it (even without the

scalac

global flag). Is this something you guys are aware or worth reporting it in Github?

Hi Alonso, this is a good channel for general Pantsbuild questions. Expect a proper reply within a few hours, when they wake up over in the US.. 😉

sure, no rush 😅

hey @witty-family-13337: this is unexpected: sorry for the trouble. it may have to do with loading multiple plugins at once, since there is some slightly ambiguous wording in the CLI args for

-Xplugin

. would you mind filing an issue with the coordinates of the two plugins, and i can check it out?

yeah, no problem, dealing with experimental features has these quirks 😉 I created ticket: https://github.com/pantsbuild/pants/issues/14011

@witty-family-13337: a quick thing to confirm: after adding the second plugin, did you re-generate the

scalac-plugins

lockfile?

./pants jvm-generate-lockfiles --resolve=scalac-plugins

I did, it seems the only thing that affects the loading of

kind-projector

is adding the

-Xplugin-list

flag (which I added just to try to debug if the plugin was being passed to scalac)

ok, thanks. and thanks for the repro.

not worries, had to verify it myself in a simpler setup than our codebase, already wasted some of your time with the coursier red herring 😉

great, thanks!

@witty-family-13337: hey Alonso! thanks again for the help. all of the relevant fixes are in

2.9.0rc2

, which was just released: https://pantsbuild.slack.com/archives/C18RRR4JK/p1641253008048900

hey, welcome, and thanks to you for being so welcoming, wish the coursier fix were ready too but it seems it’s going to take some time

@witty-family-13337: what do you mean about “the coursier fix”? i think that all known issues with coursier were resolved in this release…

Iirc there was an upstream issue Alonso reported

ah yeah, sorry I wasn’t too specific, as Eric says, an upstream one so not much that you can do for now