Fixed
Status Update
No update yet.
Comments
ja...@gmail.com
PEBKAC. Someone spelled 'UnusedResources' wrong in the XML.
Please re-purpose this bug as "Lint does not fail when invalid issue ID is referenced in XML". Not sure if it's true of the DSL config.
Please re-purpose this bug as "Lint does not fail when invalid issue ID is referenced in XML". Not sure if it's true of the DSL config.
xa...@android.com
tn...@google.com
I swear I'd fixed this but now I see that it's sitting in a local topic branch; I didn't quite finish it.
tn...@google.com
Better late than never... Fixed by Change-Id: I01759f1eb96714a61d2ea1e697462d67f9e67e89 for 3.2 beta 2.
tn...@google.com
FYI: When I integrated this in 3.2 I made unknown issue id's fail the builds;
Description
Upgrading a check to fatal in the Gradle DSL will cause it to fail the build
lintOptions {
fatal 'UnusedResources'
}
However, doing the same in an XML config does not.
lintOptions {
lintConfig file('lint.xml')
}
<lint>
<issue id="UnusedResource" severity="error"/>
</lint>
(I also tried 'fatal' as the severity value in the XML to the same effect).
I'm fairly certain this worked with the 1.3.1 plugin, but I don't have the means to test right now. At the very least it seemed to work at some point, but I'm not sure when it stopped as we don't trigger it often.
The lint output correctly does report these problems as errors, but the build does not fail. Downgrading errors to something like warning works correctly and does not fail the build.