Java annotation processing - how to handle already processed code?

Question

If I have a class

@GenerateInterface
public class _FooImpl {}

I want to generate an interface

public interface Foo {}

that basically contains all the methods of _FooImpl (i.e. getters and setters).

Also if I have inheritance, like

@GenerateInterface
public class _ParentImpl {}

@GenerateInterface
public class _ChildImpl extends _ParentImpl {}

this should result in interface inheritance as well

public interface Parent {}

public interface Child extends Parent {}

I have a rough idea how to do that. But what if _ParentImpl is part of a library? That library also has to contain Parent.

In the annotation processor, how do I handle this? I can't generate the Parent interface again because then I'd have the same interface twice. Can I somehow detect that it already exists but distinguish it from files that do also already exist but are not part of the library and can thus be overriden?

I actually only need this for one class/interface that is extended by anything else. Thus I could remove @GenerateInterface from _ParentImpl and hardcode the inheritance of the Parent interface. This would be my last resort though. Edit: Or instead of removing the interface altogether, I could set @Retention(RetentionPolicy.SOURCE), right?

An interface can't be extend a class. For inheritance among interfaces, you have to use implements. For ex: Interface_Child implements Interface_Parent — Dheeraj Kumar
– Dheeraj Kumar, Commented Aug 16, 2016 at 8:05
@DheerajRoy no that is not true. Interfaces can extend each other... — Erik Hofer
– Erik Hofer, Commented Aug 16, 2016 at 8:08
Yes Interface can extend each other, but interface cant extend a class — Dheeraj Kumar
– Dheeraj Kumar, Commented Aug 16, 2016 at 8:24
@DheerajRoy that's true. I do, however, not try to do that anywhere O.o — Erik Hofer
– Erik Hofer, Commented Aug 16, 2016 at 8:27
Your issue is not clear. Can you simplify what exactly you are trying to do? — Dheeraj Kumar
– Dheeraj Kumar, Commented Aug 16, 2016 at 9:47

Erik Hofer · Accepted Answer · 2016-08-16 11:09:40Z

1

Already compiled classes are not processed again.

I created a complete test set-up and explored the issue myself. Turns out, only files that actually have to be compiled are run through annotation processing. This means I can safely include _ParentImpl and Parent in the library. _ParentImpl can keep the annotation, it is then possible to use @Retention(RetentionPolicy.CLASS) in connection with @Inherited to apply the annotation to subclasses in a very convenient manner.

answered Aug 16, 2016 at 11:09

Erik Hofer

2,7462 gold badges24 silver badges42 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Java annotation processing - how to handle already processed code?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related