Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Hey folks, tools can't be exported using their default lockfiles. (eg, adding "pants.backend.python.lint.black" doesn't allow you to use `pants export --resolve=black`). Is there an existing way to enable that?

seems Pants requires `export` to target a user lockfile <https://github.com/pantsbuild/pants/blob/952c4cb8479f1a855b85f3f2e20511b1283f4047/src/python/pants/backend/python/goals/export.py#L312|here>.
The `generate-lockfiles` goal doesn't. Thought on enabling exporting tools from their default lockfile?

We have the same issue since upgrading to 2.18.2 from 2.17.1.

`No resolve named black found in [python].resolves.`

Did you find a solution?

The quick solution is to create a custom resolve file, like <https://www.pantsbuild.org/2.18/docs/python/overview/lockfiles#lockfiles-for-tools|here>.
I was doing some work on the backend to enable this, but fell victim to scope creep.

halfway measure, it's possible to reference the lockfile that ships with pants instead of creating a separate lockfile.
```[python.resolves]
black='<resource://pants.backend.python.lint.black/black.lock>'```
where the lockfile name is `resource://{package}/{file}`, and the values for those are found as the subsystem's `default_lockfile_resource`.
I'm more documenting this rather than suggesting it. I think it's more worthwhile to work on exporting all tools again.