Git Product home page Git Product logo

Comments (6)

tgodzik avatar tgodzik commented on June 3, 2024

Thanks for reporting! Did you try asking on the Scala plugin discord or reporting an issue with Jetbrains?

The discord link is here https://discord.gg/aUKpZzeHCK

from scalafix.

ashleymercer avatar ashleymercer commented on June 3, 2024

Ahh yes good point, having done some more digging - this only happens in IntelliJ's sbt shell, and not when using regular command-line sbt. I've cross-posted to their bug tracker:

https://youtrack.jetbrains.com/issue/IDEA-337146/sbt-projects-using-scalafix-repeatedly-warn-of-Unrecognized-repository

from scalafix.

bjaglin avatar bjaglin commented on June 3, 2024

Per this commit, it looks like the issue arise when the IntelliJ sbt plugin is injected into a project using sbt-coursier, and is fixed in recent 2023.3.x IntelliJ versions.

from scalafix.

bjaglin avatar bjaglin commented on June 3, 2024

I confirm that users of IntelliJ < 2023.3.2 running projects with ScalafixTestkitPlugin are impacted through the usage of includePluginResolvers.

I am still trying to figure out what's going on. Until then, this workaround seems to work for https://github.com/ashleymercer/scalafix-issue-1887:

ThisBuild / includePluginResolvers := false

from scalafix.

bjaglin avatar bjaglin commented on June 3, 2024

I am still trying to figure out what's going on.

  • it looks like there are different code paths for the build and the metabuild (coursier vs ivy?)
  • by construction, includePluginResolvers := true exposes the plugin resolver added by the IntelliJ sbt plugin to a code path not exercised in the default case: the build one, driven by lm-coursier-shaded as published by sbt-coursier
  • the plugin resolver, as declared before IntelliJ 2023.3.2, was not valid for that code path, generating the warning in all update tasks of the build (without any impact as the resolver is only needed in the metabuild)

I'll close this as this is fixed in the latest IntelliJ version, and there is a workaround above for the older ones. Thanks again for the report, feel free to reopen if my analysis is wrong.

from scalafix.

ashleymercer avatar ashleymercer commented on June 3, 2024

Awesome detective work @bjaglin - thanks!

Yes can confirm this is fixed in the EAP builds of 2023.3 so happy for this to be closed.

from scalafix.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.