Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
The problem to solve here is false positive warnings about unused classes that are not directly instantiated by the code, but plugged in via some reflective mechanism.
The suggestion is to introduce a marker annotation, that we can use to mark such implementation classes, in IntelliJ it is possible to filter out unused declaration warning on items based on annotation, so it seems to be a feasible solution.
An additional gain from this is the possibility to connect the code to the corresponding configuration via a short description added to the code itself, with the potential to check based on the annotation that these classes are never instantiated (if we want to implement such a check).