annotation processor creates wrong files under certain conditions #264
I'm currently migrating my application from JPF to pf4j and discovered a problem in the
I'm using the following pattern to define extension points and extensions:
In contrast to your examples there are abstract classes (
Basically this approach also works with pf4j. But the
Because of this problem the
I'm going to propose a pull request with a possible workaround for this problem.
The text was updated successfully, but these errors were encountered:
This is a workaround for issue pf4j#264. An extension may provide its implemented extension points explicitly through its annotation. In this case the annotation processor does not try to detect the extension points for an extension automatically (which fails under certain conditions).
Thanks again for detailed explanation. Now, the case with adapters doesn't work. The adapters are see as extensions by PF4J.