IssueTracker

Oh, worth noting that rule from that sample project works fine if Lint run via console.

+1

Something needs to trigger building the lint artifact, but as a workaround, here's what I did which made it work:

1. Opened the sample project in Flamingo, and used the upgrade assistant to update it to 8.0.0-alpha10 (the same version of Flamingo I was using)
2. Opened the test file ("Test) -- there's no lint warning yet
3. Opened the terminal window inside the IDE (Help > Find Action > terminal)
4. Ran "./gradlew lint"

That triggered a build, and once it finished, the IDE also updated to start showing the lint warning without me having to do anything else (see screenshot).

Something needs to trigger building the lint artifact

Here are 2 options that come to mind:

1. Trigger building the lint.jar file during sync.
2. Add a dependency from common build commands (e.g., assembleDebug) to the task that creates the lint.jar file (so that at least the lint.jar file would exist more often than it does now).

Chris, do you have more context to suggest the best way forward? Both of these seem like they might cause performance regressions, and I'm not sure that option 1 is even allowed.

Yes, I agree we need a way to do this, but also that those options both have downsides as Scott identifies.

I wonder if we need to have a 'build custom lint checks' action in the IDE, maybe with some level of prompting to trigger it in Studio if we detect that the user has configured their project to have custom lint rules but they're not built yet.