import to fix local build failure

[samspills]

Without this import, loading the build locally would fail with the following:

/Users/sam_1/src/github.com/http4s/sbt-http4s-org/build.sbt:14: error: No implicit for Remove.Value[explicitdeps.ModuleFilter, sbt.librarymanagement.ModuleFilter] found,
  so sbt.librarymanagement.ModuleFilter cannot be removed from explicitdeps.ModuleFilter
    unusedCompileDependenciesFilter -= moduleFilter("org.typelevel", "sbt-typelevel"),
                                    ^
sbt.compiler.EvalException: Type error in expression

I'm not sure why it hasn't been failing in CI though?

[armanbilge]

Huh, this is so weird. I can't reproduce locally.

$ sbt -version
sbt version in this project:    1.10.3
sbt script version: 1.10.3

[rossabaker]

I can reproduce it going back to the commit that added it. I don't have any working theory why.

[samspills]

Just for reference, I have the same versions on this branch, and on main I get

❯ sbt -version
/Users/sam_1/src/github.com/http4s/sbt-http4s-org/build.sbt:14: error: No implicit for Remove.Value[explicitdeps.ModuleFilter, sbt.librarymanagement.ModuleFilter] found,
  so sbt.librarymanagement.ModuleFilter cannot be removed from explicitdeps.ModuleFilter
    unusedCompileDependenciesFilter -= moduleFilter("org.typelevel", "sbt-typelevel"),
                                    ^
sbt.compiler.EvalException: Type error in expression
[warn] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? (default: r)
sbt script version: 1.10.3

I was getting 1.10.2 for the script version originally, but I updated and I'm still getting the error so I don't think that was the cause of anything.

[armanbilge]

Do you have some global sbt plugins configured? That's the only other thing I can imagine would be affecting your environment.

[samspills]

I do, I have sbt-dependency-graph, sbt-updates, and sbt-vimquit

[rossabaker]

I've isolated it to a global sbt-updates.

[samspills]

Huh. I couldn't remember why I'd added sbt-updates so I deleted that one, and the error went away. Adding it back in reproduces. @rossabaker do you have that plugin also?

yeah, he does 😆

[rossabaker]

And here's why. The two implicits have the same name.

[samspills]

I think it still makes sense to move forward with adding the import, right? It's not going to cause a problem to have it, and it'll prevent stumbling for folks who do have a global sbt-updates set up.

[rossabaker]

A better solution would be to get the upstream plugins to rename theirs, but I don't think this hurts anything in the interim, and it helps at least two of us.