errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2661545232

   IIUC, `JUL` can not be a bridge source; so currently NB does not support 
generating code that can be a logging bridge source. Adding `System.Logger` 
allows generating code that can bridge to the well known loggers. This is in 
some sense a bug fix, at least in the past NB supported new Java features as 
they came out. In addition to what's been discussed, a set of hints that 
converts from `JUL` to `System.Logger` could be useful; use with `Refactor > 
Inspect and Transform...`.
   
   If NB want to support code generation for 3rd party logging, IMHO anything 
less than an extensible infrastructure misses the mark. Different projects 
probably have different standards. I wouldn't be surprised if different 
projects that use the same backend logger have different standards for how the 
logging is used. I wonder how many projects are around that still use custom 
logging implementations. In NB, there is not only code generation, but 
additional hints that look for standards/style violations (I've added a list 
from NB of things I'm aware to the end of the OP). Each logger, or logger 
style, that is added should specify not only code generation, but also standard 
checks and rewrites for use with existing hints. Additional and/or custom 
logger hints should also be considered that are useful for enterprise projects. 
Might want to register a set of hints that convert from one logger framework to 
another. It may be that per project specification is too coarse grained 
(thinking
  about some of the previous comments in this thread); and so a set of roots 
should be specified for a given logger/style.
   
   It took me a little while but I finally remember that NetBeans has 
`layer.xml`, supplemented later with annotatations. Extension points are 
defined for registration. I can't imagine why this wouldn't be used for 
specifying 3rd party loggers/styles.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org
For additional commands, e-mail: notifications-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to