@Generated not found javax.annotation.processing.Generated #1339

ayvazj · 2018-11-19T15:58:40Z

I am seeing this issue when trying to compile an Android project with Dagger2 (Google I/O 2018 sample app).

package javax.annotation.processing does not exist
import javax.annotation.processing.Generated;

I have tried the several solutions mentioned in the issues and stack overflow for resolving javax.annoation.Generated but not having any luck. Note the annotation is in the javax.annotation.processing package.

The text was updated successfully, but these errors were encountered:

ronshapiro · 2018-11-19T16:00:02Z

Are you using -source 9 in your compilation (perhaps implicitly)? What do you get if you run javac -version?

YuraAAA · 2018-11-19T17:00:41Z

Are you using -source 9 in your compilation (perhaps implicitly)? What do you get if you run javac -version?

Same issue on my teamcity CI server (clean assembleDebug).

javac -version
javac 1.8.0_181

But on local PC works fine

$ javac -version
javac 1.8.0_162

Dependencies:

implementation "com.google.dagger:dagger:$dagger_version"
kapt "com.google.dagger:dagger-compiler:$dagger_version"
kapt "com.google.dagger:dagger-android-processor:$dagger_version"
implementation "com.google.dagger:dagger-android-support:$dagger_version"

where
dagger_version = '2.16'

Error

[Step 1/2] :app:compileDebugJavaWithJavac

package javax.annotation.processing does not exist
[19:54:12][:app:compileDebugJavaWithJavac] import javax.annotation.processing.Generated;
...
 error: cannot find symbol
[19:54:12][:app:compileDebugJavaWithJavac] @Generated

ayvazj · 2018-11-19T17:04:30Z

I am using (for Android)

compileOptions {
  sourceCompatibility JavaVersion.VERSION_1_8
  targetCompatibility JavaVersion.VERSION_1_8
}

I have also manually tried setting JAVA_HOME to jdk1.8 and jdk9 - same result.

ayvazj · 2018-11-20T03:14:59Z

My issue turned out to be related to JDK9 - explicitly using JDK 1.8 resolved the issue for me. ¯\_(ツ)_/¯

Add the following to gradle.properties

org.gradle.java.home={PATH TO JAVA 8}

Note setting JAVA_HOME did not work for me

YuraAAA · 2018-11-20T11:24:28Z

My issue turned out to be related to JDK9 - explicitly using JDK 1.8 resolved the issue for me. ¯_(ツ)_/¯

Add the following to gradle.properties
org.gradle.java.home={PATH TO JAVA 8}
Note setting JAVA_HOME did not work for me

Thank you. I checked my environment and found jdk11 and jdk8. Uninstall and reinstall only jdk8 removed this error.

morymmm · 2018-11-21T12:54:28Z

I am seeing the same issue when trying to compile with JDK10:

package javax.annotation.processing does not exist import javax.annotation.processing.Generated;

tbroyer · 2018-11-21T13:47:55Z

Fwiw, with 2.14 (using auto-common 0.9), Dagger will use @javax.annotation.processing.Generated unless --release 8 is used (in which case @javax.annotation.Generated will be used instead):

tasks.withType(JavaCompile) {
  options.compilerArgs += [ "--release", "8" ]
}

From 2.15 onward (using auto-common 0.10), Dagger will also respect -source 8 -target 8, i.e. Gradle's sourceCompatibility and targetCompatibility.

morymmm · 2018-11-27T10:02:41Z

I have created a simple android application written in kotlin with an empty dagger component:

@Component
interface AppComponent { }

apply plugin: 'kotlin-kapt'

dependencies {
    implementation 'com.google.dagger:dagger:2.19'
    kapt 'com.google.dagger:dagger-compiler:2.19'
}

When trying to compile with dagger 2.19 and JDK10 dagger adds javax.annotation.processing.Generated annotation to DaggerAppComponent class and compilation fails with:

error: package javax.annotation.processing does not exist
error: cannot find symbol @Generated

Compiling with JDK8 works fine. There is no @generated annotation added. When I switch to dagger 2.13 it does not add @generated for both JDK10 and JDK8.

contrudar · 2018-12-18T12:34:29Z

there is no way to make it work with Java 11?

contrudar · 2018-12-18T14:03:05Z

My issue turned out to be related to JDK9 - explicitly using JDK 1.8 resolved the issue for me. ¯_(ツ)_/¯

Add the following to gradle.properties
org.gradle.java.home={PATH TO JAVA 8}
Note setting JAVA_HOME did not work for me

just in case, if you don't want to put it to gradle.properties, you can use gradlew TASK_NAME -Dorg.gradle.java.home="C:\Program Files\Android\Android Studio\jre" . This is useful for CI or if several people work on the same project.

almozavr · 2019-01-16T21:54:36Z

From 2.15 onward (using auto-common 0.10), Dagger will also respect -source 8 -target 8, i.e. Gradle's sourceCompatibility and targetCompatibility.

Unfortunately, it doesn't work for android projects. Any tip how we can compile android, jdk9+ and dagger?

pengrad · 2019-02-10T11:41:52Z

Unfortunately, it doesn't work for android projects. Any tip how we can compile android, jdk9+ and dagger?

Manually create Generated interface in your project. There could be package exists in another module: java.compiler error if adding in android app module, but creating in android-library module (and then adding it to main via implementation project(':module-generated')) works fine.

I've uploaded package with such class to JCenter https://github.com/pengrad/jdk9-deps
Now it's possible to just add this gradle dependency and it compiles with JDK11:
compileOnly 'com.github.pengrad:jdk9-deps:1.0'

ronshapiro · 2019-03-25T21:05:57Z

Let's converge on #1449 which seems to be the same, and advanced pretty quickly. In particular it seems like there's a kapt bug that will be linked there.

pvthiendeveloper · 2019-12-31T06:24:40Z

Unfortunately, it doesn't work for android projects. Any tip how we can compile android, jdk9+ and dagger?

Manually create Generated interface in your project. There could be package exists in another module: java.compiler error if adding in android app module, but creating in android-library module (and then adding it to main via implementation project(':module-generated')) works fine.

I've uploaded package with such class to JCenter https://github.com/pengrad/jdk9-deps
Now it's possible to just add this gradle dependency and it compiles with JDK11:
compileOnly 'com.github.pengrad:jdk9-deps:1.0'

It work for me. Thank you so much!

…ion issues. Updates in typings.

ericntd · 2020-09-28T16:54:05Z

Thanks a lot @pengrad , I think I'm very close.
Having the same issue with Intellij 2020.* and Android Studio 4.2 Preview and Dagger 2.22

My team doesn't approve the external dependency of com.github.pengrad:jdk9-deps:1.0 so I went ahead and create a "Android Library" project called "javax-generated" with 1 single class like the one in your repo:

package javax.annotation.processing;
public @interface Generated {
    String[] value();

    String date() default "";

    String comments() default "";
}

It's all well and good in my library modules, however, it's not working for my :app module:

implementation(project(':javax-generated')) gives

e: /Users/ericn/AndroidStudioProjects/Folder/Project/app/build/generated/not_namespaced_r_class_sources/debug/processDebugResources/r/javax/annotation/processing/R.java:7: error: package exists in another module: java.compiler
package javax.annotation.processing;

compileOnly(project(':javax-generated')) gives

Android dependency 'project :javax-generated' is set to compileOnly/provided which is not supported

Any idea what I'm missing?

MichalDanielDobrzanski · 2020-10-07T12:02:21Z

@ericntd I am facing the same problems on Android Studio 4.2 Preview and Dagger 2.22.

I was not able to use this com.github.pengrad:jdk9-deps:1.0 external dependency inside my project - gradle complained that javax annotation is still missing.

I was trying with: compileOnly("javax.annotation:jsr250-api:1.0") dependency, which provide official JSR250 annotations, but with no luck.

ericntd · 2020-10-21T15:14:08Z

The issue seems to have gone away with Android Studio 4.2 Canary 14 @MichalDanielDobrzanski

tobenna-paystack · 2020-10-23T12:36:43Z

The issue seems to have gone away with Android Studio 4.2 Canary 14 @MichalDanielDobrzanski

Having same issue with Canary 14

processors generate source that matches the target version. For example see: google/dagger#1339

* Fix breakages in experimental_use_java_builder flow. Make examples/android use custom toolchain with both experimental_use_abi_jars and experimental_use_java_builder to validate this flow. * Pass Java source version for KAPT. This is required such that annotation processors generate source that matches the target version. For example see: google/dagger#1339 * ABI classes should be written to a separate folder to avoid polluting the ABI jar with non-ABI classes * Maintain mnemonic to distinguish between KotlinKapt + KotlinCompile (Both belong to the same worker group) * Add default java + kotlin compiler options

phillipsk · 2021-01-07T20:15:27Z

Also having issues with the Canary release, instead installed the stable AS release v4.1 at the time of writing and since have no issues with the stable AS

techker · 2021-04-21T17:53:24Z

4.2 preview same issue. if i use 4.0 works..whats the issue?

sasfmlzr · 2021-04-22T20:04:07Z

4.2 preview same issue. if i use 4.0 works..whats the issue?

If you are updating your android studio and using arctic fox (2020.3.1) don't forget to update the gradle plugin.
classpath "com.android.tools.build:gradle:7.0.0-alpha14"

pandelisgreen13 · 2021-05-05T08:38:36Z

with the stable Android Studio 4.2, I have the same problem with Dagger 2.25, after I updated dagger to latest version, the problem solved

rathorerahul586 · 2021-05-05T12:22:47Z

with the stable Android Studio 4.2, I have the same problem with Dagger 2.25, after I updated dagger to latest version, the problem solved

@pandelisgreen13 are you using the room library in the project?

appscore-ahmed · 2021-05-05T12:28:19Z

Updating the dagger version doesnt work for me. Is there any other way to resolve this issue? I have explicitly selected Source Compatibility and Target Compatibility as 1_8, while my mac has java 9 installed.

pandelisgreen13 · 2021-05-05T12:52:48Z

with the stable Android Studio 4.2, I have the same problem with Dagger 2.25, after I updated dagger to latest version, the problem solved

@pandelisgreen13 are you using the room library in the project?

Yes, we have Room
With the modules that they had the problem with dagger, I had to set Java 8 at gradle

sourceCompatibility = JavaVersion.VERSION_1_8
targetCompatibility = JavaVersion.VERSION_1_8

rathorerahul586 · 2021-05-05T13:02:40Z

me too using the same but getting issue

Execution failed for task ':app:kaptAppNameKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution
   > java.lang.reflect.InvocationTargetException (no error message)

at last, downloaded the previous version 4.1.3 after wasting too much time.

eagskunst · 2021-05-05T16:58:07Z

Had this issue with Android Studio 4.2. Tried solutions from above and what finally worked was to update Kotlin from 1.3.50 to 1.4.31.

VuXuanBach · 2021-05-06T06:04:52Z

Also, make sure to update gradle plugin to 4.2.0 according to this https://developer.android.com/studio/releases/gradle-plugin#4-2-0

lucianbc · 2021-05-08T12:47:39Z

I recently had this issue on a project when migrating to java 11. I figured out the issue was caused by me using an outdated version of assisted-inject. I made it work by updating dagger to 2.35.1 and both of my assisted-inject dependencies to 0.8.1:

compileOnly 'com.squareup.inject:assisted-inject-annotations-dagger2:0.8.1'
kapt 'com.squareup.inject:assisted-inject-processor-dagger2:0.8.1'

danielwilson1702 · 2021-05-17T17:04:45Z

I get this on a very under-developed project, fix was to update Dagger from 2.14.1 to 2.25.4 (before Android X as my project is not upgraded yet). About time to do that methinks.

laperezh · 2021-05-19T17:02:30Z

I recently had this issue on a project when migrating to java 11. I figured out the issue was caused by me using an outdated version of assisted-inject. I made it work by updating dagger to 2.35.1 and both of my assisted-inject dependencies to 0.8.1:
compileOnly 'com.squareup.inject:assisted-inject-annotations-dagger2:0.8.1'
kapt 'com.squareup.inject:assisted-inject-processor-dagger2:0.8.1'

This

Also, make sure to update gradle plugin to 4.2.0 according to this https://developer.android.com/studio/releases/gradle-plugin#4-2-0

And this, did it for me on Android Studio 4.2.1. Thank you very very very much.

Sanaebadi97 · 2021-11-17T09:02:09Z

I was using Java 11 and I change it to 1.8 and this issue fixed.

  compileOptions {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

joaodevsantos · 2022-03-02T16:06:03Z

Unfortunately, it doesn't work for android projects. Any tip how we can compile android, jdk9+ and dagger?

Manually create Generated interface in your project. There could be package exists in another module: java.compiler error if adding in android app module, but creating in android-library module (and then adding it to main via implementation project(':module-generated')) works fine.

I've uploaded package with such class to JCenter https://github.com/pengrad/jdk9-deps Now it's possible to just add this gradle dependency and it compiles with JDK11: compileOnly 'com.github.pengrad:jdk9-deps:1.0'

I have this issue this morning and after spent hours on trying different things and Java versions, this fixed my problem. So, add compileOnly 'com.github.pengrad:jdk9-deps:1.0' to my build.gradle files fix the issue.

swetab2 · 2022-04-03T05:36:35Z

this add in dependency.

// implementation 'javax.annotation:javax.annotation-api:1.3.2'

* Fix breakages in experimental_use_java_builder flow. Make examples/android use custom toolchain with both experimental_use_abi_jars and experimental_use_java_builder to validate this flow. * Pass Java source version for KAPT. This is required such that annotation processors generate source that matches the target version. For example see: google/dagger#1339 * ABI classes should be written to a separate folder to avoid polluting the ABI jar with non-ABI classes * Maintain mnemonic to distinguish between KotlinKapt + KotlinCompile (Both belong to the same worker group) * Add default java + kotlin compiler options

miraboh · 2022-04-20T20:47:49Z

Close ide, navigate to project folder, delete build folder(contains generated file etc), then launch project in ide again, that solve the issue.

AndresBPaz · 2023-01-16T22:13:31Z

Thanks a lot @pengrad , I think I'm very close. Having the same issue with Intellij 2020.* and Android Studio 4.2 Preview and Dagger 2.22

My team doesn't approve the external dependency of com.github.pengrad:jdk9-deps:1.0 so I went ahead and create a "Android Library" project called "javax-generated" with 1 single class like the one in your repo:
package javax.annotation.processing;
public @interface Generated {
    String[] value();

    String date() default "";

    String comments() default "";
}
It's all well and good in my library modules, however, it's not working for my :app module:

implementation(project(':javax-generated')) gives
e: /Users/ericn/AndroidStudioProjects/Folder/Project/app/build/generated/not_namespaced_r_class_sources/debug/processDebugResources/r/javax/annotation/processing/R.java:7: error: package exists in another module: java.compiler
package javax.annotation.processing;
compileOnly(project(':javax-generated')) gives
Android dependency 'project :javax-generated' is set to compileOnly/provided which is not supported
Any idea what I'm missing?

I tried it in spring boot with java 1.8 and it doesn't let me run the project after including it in my clashpath

muneeb-saadii · 2023-07-16T02:30:54Z

Just add this dependency

implementation 'javax.annotation:javax.annotation-api:1.3.2'

pmatsinopoulos · 2023-08-08T12:39:50Z

me too using the same but getting issue
Execution failed for task ':app:kaptAppNameKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution
   > java.lang.reflect.InvocationTargetException (no error message)
at last, downloaded the previous version 4.1.3 after wasting too much time.

@rathorerahul586 .... previous version of what?

rathorerahul586 · 2023-08-08T13:33:21Z

me too using the same but getting issue
Execution failed for task ':app:kaptAppNameKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptExecution
   > java.lang.reflect.InvocationTargetException (no error message)
at last, downloaded the previous version 4.1.3 after wasting too much time.
@rathorerahul586 .... previous version of what?

Android Studio

baderkhane · 2023-09-06T11:14:02Z

I fixed the issue with

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    kotlin {
        jvmToolchain(8)
    }

google/dagger#1339

ronshapiro closed this as completed Mar 25, 2019

tonisives mentioned this issue Jan 29, 2020

javax annotation does not exist AkshayChordiya/News#32

Closed

AlexMiniApps referenced this issue in AlexMiniApps/cordova-plugin-video-editor Sep 15, 2020

Android updates: Switching from File to FileDescriptor due to permiss…

9680cac

…ion issues. Updates in typings.

jongerrish added a commit to jongerrish/rules_kotlin that referenced this issue Nov 23, 2020

Pass Java source version for KAPT. This is required such that annotation

3091a34

processors generate source that matches the target version. For example see: google/dagger#1339

nikhiljha mentioned this issue Dec 3, 2020

Memory Allocation Failure / Crash on Startup streetcomplete/StreetComplete#2336

Closed

bcorso mentioned this issue May 11, 2021

update the android studio to 4.2 then has a problem #2608

Closed

matkoniecz mentioned this issue Oct 11, 2021

special speed zone sign layout for many countries streetcomplete/StreetComplete#3359

Merged

46 tasks

tompee26 mentioned this issue Oct 20, 2021

Generated annotation not found when compiling against Java 11 ansman/kotshi#173

Closed

hondayuki0606 added a commit to hondayuki0606/BabyDiaryCompose that referenced this issue Mar 21, 2024

BDT-123, Composeのhiltのテストに失敗するがjavaを1.8にすれば解決するかもしれない

a67f9cb

google/dagger#1339

infeo mentioned this issue Jun 4, 2024

Update of different dependency: Error "package javax.annotation.processing is not visible" #4321

Closed

@Generated not found *javax.annotation.processing.Generated* #1339

@Generated not found *javax.annotation.processing.Generated* #1339

Comments

ayvazj commented Nov 19, 2018

ronshapiro commented Nov 19, 2018

YuraAAA commented Nov 19, 2018 • edited Loading

ayvazj commented Nov 19, 2018

ayvazj commented Nov 20, 2018 • edited Loading

YuraAAA commented Nov 20, 2018

morymmm commented Nov 21, 2018

tbroyer commented Nov 21, 2018

morymmm commented Nov 27, 2018 • edited Loading

contrudar commented Dec 18, 2018

contrudar commented Dec 18, 2018 • edited Loading

almozavr commented Jan 16, 2019

pengrad commented Feb 10, 2019

ronshapiro commented Mar 25, 2019

pvthiendeveloper commented Dec 31, 2019

ericntd commented Sep 28, 2020 • edited Loading

MichalDanielDobrzanski commented Oct 7, 2020

ericntd commented Oct 21, 2020

tobenna-paystack commented Oct 23, 2020

phillipsk commented Jan 7, 2021

techker commented Apr 21, 2021

sasfmlzr commented Apr 22, 2021 • edited Loading

pandelisgreen13 commented May 5, 2021

rathorerahul586 commented May 5, 2021 • edited Loading

appscore-ahmed commented May 5, 2021

pandelisgreen13 commented May 5, 2021

rathorerahul586 commented May 5, 2021 • edited Loading

eagskunst commented May 5, 2021

VuXuanBach commented May 6, 2021

lucianbc commented May 8, 2021

danielwilson1702 commented May 17, 2021

laperezh commented May 19, 2021

Sanaebadi97 commented Nov 17, 2021

joaodevsantos commented Mar 2, 2022

swetab2 commented Apr 3, 2022

miraboh commented Apr 20, 2022 • edited Loading

AndresBPaz commented Jan 16, 2023

muneeb-saadii commented Jul 16, 2023

pmatsinopoulos commented Aug 8, 2023

rathorerahul586 commented Aug 8, 2023

baderkhane commented Sep 6, 2023

@Generated not found javax.annotation.processing.Generated #1339

@Generated not found javax.annotation.processing.Generated #1339

YuraAAA commented Nov 19, 2018 •

edited

Loading

ayvazj commented Nov 20, 2018 •

edited

Loading

morymmm commented Nov 27, 2018 •

edited

Loading

contrudar commented Dec 18, 2018 •

edited

Loading

ericntd commented Sep 28, 2020 •

edited

Loading

sasfmlzr commented Apr 22, 2021 •

edited

Loading

rathorerahul586 commented May 5, 2021 •

edited

Loading

rathorerahul586 commented May 5, 2021 •

edited

Loading

miraboh commented Apr 20, 2022 •

edited

Loading