Chris Kipp

> Is this the reason for [scalameta/metals#2279](https://github.com/scalameta/metals/pull/2279) ? I don't believe so. I still don't know what's going on there. When I compare the json files for 1.4.2 and 1.4.3...

So it looks like this may be wart remover specific. This commit is the one that seems to have caused it https://github.com/wartremover/wartremover/commit/fadeadc174a10874e301ca4d6161f0a1751fc330 since they needed to go away from the...

> Seems like a lot of fun 😅. I'll give it a try! That would be incredible @kpodsiad! I'll go ahead and assign you on here just to ensure someone...

Popping in here. I really don't think we should close this without some type of action signifying that this isn't supported. I'm trying to do some work on the plugin...

This sounds like a great idea. One thing that does come to mind though is that how would this work for a build server that isn't the same tool as...

> > What should code be in FailedBuildTarget? > > Probably we don't need it. Either that or do you think it'd be useful to also have space for an...

> What would IDEs do with the failures? Would they show a message saying that some build targets could not be resolved? I believe on the Metals side we more...

> Yes of course. I am just saying that code is probably useless but message should be mandatory and we can also have an optional data. Ach, I totally misread...

> Hi @ckipp01, what's the state of this? Could you bump this to zinc 1.7.0? Yea, later this week I should have some time to look back at this, but...

I honestly have no idea what's going on with this. I was able to get this added to sbt by just mapping the diagnostic code pretty easily in https://github.com/sbt/sbt/pull/6998/files, but...