Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
Reviewed
Description
A bunch of the actions all use the same logger inherited from the super class. We should have them declare distinct loggers, either each one in class or perhaps we can do something dynamically like LogFactory.getLogger(MethodHandles.lookup().lookupClass() and drop the static modifier on the log field.
I'm not sure that exact incantation would actually work, but the MethodHandles approach in general is how logger resolution happens in Solr and it actually works out pretty well.
Attachments
Issue Links
- links to