8000 Unexpected error when using @AfterViews · Issue #433 · androidannotations/androidannotations · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

Unexpected error when using @AfterViews #433

@hanbo

Description

@hanbo

Sometimes i get the following error in methods that are using @AfterViews with the HoloEverywhere patched version of android annotations from mikegr #429

Unexpected error. Please report an issue on AndroidAnnotations, with the following content: java.lang.RuntimeException: javax.annotation.processing.FilerException: Source file already created: /XXX/.apt_generated/org/androidannotations/api/SdkVersionHelper.java
    at org.androidannotations.generation.ApiCodeGenerator.writeApiClasses(ApiCodeGenerator.java:79)
    at org.androidannotations.generation.CodeModelGenerator.generate(CodeModelGenerator.java:40)
    at org.androidannotations.AndroidAnnotationProcessor.generateSources(AndroidAnnotationProcessor.java:598)
    at org.androidannotations.AndroidAnnotationProcessor.processThrowing(AndroidAnnotationProcessor.java:381)
    at org.androidannotations.AndroidAnnotationProcessor.process(AndroidAnnotationProcessor.java:342)
    at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.handleProcessor(RoundDispatcher.java:139)
    at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:110)
    at org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:159)
    at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:134)

It happens in classes that are referencing each other. Eg. in MainActivity i have somewhere LoginActivity_.intent(this).start(); and in LoginActivity a MainActivity_.intent(this).start();

My workaround is to comment out one of the references of the classes. Then they can be build without the error above and i can comment the reference back in and everything is fine. But thats not a real solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0