Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failure : 'options.compilerArgumentProviders.errorprone$0.name' is missing an input or output annotation. #931

Closed
TeenaJoseph opened this issue Mar 11, 2024 · 1 comment

Comments

@TeenaJoseph
Copy link

TeenaJoseph commented Mar 11, 2024

A problem was found with the configuration of task ':app:compileEmuDebugJavaWithJavac' (type 'JavaCompile').
  - Type 'org.gradle.api.tasks.compile.JavaCompile' property 'options.compilerArgumentProviders.errorprone$0.name' is missing an input or output annotation.
    
    Reason: A property without annotation isn't considered during up-to-date checking.

    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.

Environment:
Gradle version 7.5
Android Java Project

build.gradle Code snippet:

plugins {
    // ... other plugins
    id "net.ltgt.errorprone" version "3.1.0" // Optional
}

dependencies {
    //nullaway
    errorprone "com.uber.nullaway:nullaway:0.10.24"
    compileOnly "com.google.code.findbugs:jsr305:3.0.2"
    errorprone "com.google.errorprone:error_prone_core:2.25.0"
import net.ltgt.gradle.errorprone.CheckSeverity

tasks.withType(JavaCompile) {
    options.incremental = false//set to true for incremental build
    // remove the if condition if you want to run NullAway on test code
    if (!name.toLowerCase().contains("test")) {
        options.errorprone {
            check("NullAway", CheckSeverity.ERROR)
            option("NullAway:AnnotatedPackages", "com.example")
        }
    }
}
@msridhar
Copy link
Collaborator

Sorry, I don't have enough context to understand what's happening here, but note that net.ltgt.errorprone no longer supports Android; see here for details.

I don't think this is a NullAway issue, so I'm going to go ahead and close. But please comment if you have more evidence this is related to NullAway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants