-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Annotation processor can't handle more than 5 library modules #4106
Comments
Huh, I have a project with 10 library modules at Google. I wonder if the name limit varies by the specific compiler. We can probably do something more intelligent by trading off readability. I'm not even sure it's intentional that any particular indexer has every single module and package name listed... |
May be just Windows 10, what happens if you build the sample project? |
Also, maybe worth looking how Dagger Components handle Modules. Never had a problem even with lots of modules. |
Reproduces on OSX: > java.lang.RuntimeException: java.nio.file.FileSystemException: /Users/judds/opensource/repros/glide/apt_many_libs/build/generated/ap_generated_sources/debug/out/com/bumptech/glide/annotation/compiler/GlideIndexer_GlideModule_com_example_application_pack_age_LibModule6_com_example_application_pack_age_LibModule1_com_example_application_pack_age_LibModule3_com_example_application_pack_age_LibModule2_com_example_application_pack_age_LibModule5_com_example_application_pack_age_LibModule4.java: File name too long |
Ooh, cool, thanks! What is this indexer btw? |
Glide Version: 4.12.0
Integration libraries: none / all
Device/Android Version: all
Build system: Gradle 5.6.4 on Windows 10
Issue details / Repro steps / Use case background:
Having 5-6 library modules in the project (depending on package and class names) stops AppGlideModule from compiling.
gradlew assembleDebug --stacktrace
-> failsExpected:
same behavior as when there are less modules, e.g.
LibModule6.java
, or comment it out, or remove@GlideModule
.gradlew assembleDebug --stacktrace
-> all goodActual: see stack trace.
Glide load line /
GlideModule
(if any) / list Adapter code (if any):Layout XML: N/A
Stack trace / LogCat:
Execution failed for task ':compileDebugJavaWithJavac'.
The text was updated successfully, but these errors were encountered: