You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@netbeans.apache.org by "errael (via GitHub)" <gi...@apache.org> on 2025/02/12 23:42:43 UTC
[I] consider `System.Logger` in related hints/code-generation [netbeans]
errael opened a new issue, #8240:
URL: https://github.com/apache/netbeans/issues/8240
### Description
This affects (the hints are under `Options > Editor > Hints > Java`)
- `Insert Code` action/dialog, aka `Generate > Logger...`
- `Surround with try-catch` hint, under `Error Fixes` hints
- `Logging` hints
There might be other items that should be added to the above list.
A key question is how to specify which Logger, between `System` and `java.util`, to use. Could
1. Add a new option somewhere; like a new tab under `Tools > Options`, examples
- `Tools > Options > Java > Java Logging`
- `Tools > Options > Java > Java` for future looking
2. Extend list at `Tools > Options > Editor > Hints > Java > Surround with try-catch`
with `Use java.lang.System.Logger`
Doing (2) above is the simplest. I'd be inclined to put it above `java.util` and have it check-marked by default. Consider that in most instances at run-time, there is little practical difference from the current behavior. These options could be used by `Generate > Logger...`, and in other cases as needed, to select which of the two loggers to use to initialize the logger. If this is acceptable, I volunteer.
A few additional things that could be done
A "use existing logger" option for `Surround with try-catch`.
For reference, here the current and proposed code.
- Current
- `Generate>Logger...`
`private static final Logger LOG = Logger.getLogger(Mavenproject5.class.getName());`
- `Surround with try-catch`
`Logger.getLogger(Mavenproject5.class.getName()).log(Level.SEVERE, null, ex);`
- Proposed (when option is for System.Logger)
- `Generate>Logger...`
`private static final Logger LOG = System.getLogger(Mavenproject5.class.getName());`
- `Surround with try-catch`
- `System.getLogger(Mavenproject5.class.getName()).log(Level.ERROR, null, ex);`
- `LOG.log(Level.ERROR, null, ex);` // If "use existing logger" implemented
Additional `Generate>Logger...` options for consideration
- specify name of generated logger, e.g. "logger" instead of "LOG"
- expression to use to init logger, e.g. "Utils.getLogger()" vs System.getLogger(...)
With these options, a generated logger would look like
```
private static final Logger logger = Utils.getLogger();
```
### Use case/motivation
Provide access to newer, as of Java-9, capability
### Related issues
_No response_
### Are you willing to submit a pull request?
Yes
--
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-unsubscribe@netbeans.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] Additional features for working with `Logger`s [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2764809895
Now that #8253 is merged, the OP is modified to summarize additional features for working with loggers (title changed as well).
Most of the OP's new text is derived from discussion already in this issue.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "matthiasblaesing (via GitHub)" <gi...@apache.org>.
matthiasblaesing commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2659888298
> > If this is touched, other logging frameworks should also be considered. SLF4J/Log4J2/Logback/commons-logging all can be valid selections for logging. It would be good if this would be per project.
>
> Before `Java 9` I would 100% agree. But now, doesn't `System.Logger` make all of these selectable at run-time rather than hard-coding?
SLF4J existed for how long? Sorry, but I see https://xkcd.com/927/ here. Just as the module system of java faces an uphill battle, the same is true for logging systems.
I have projects where the framework mandates logback, a CMS that mandates SLF4J and has legacy use of log4j, local projects that use JUL. Only the latter could be changed, all others have to integrate with their corresponding ecosystem.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "mbien (via GitHub)" <gi...@apache.org>.
mbien commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2660044291
> In addition to stuff mentioned in the OP, there is also stuff in Tools > Options > Editor > Code Templates. Is this what you're talking about?
yes, although I don't know how many are visible through that window. Things like https://github.com/apache/netbeans/pull/3458 etc are usually all solved with templates.
> 2. Extend list at Tools > Options > Editor > Hints > Java > Surround with try-catch
with Use java.lang.System.Logger
yep, updating this hint would be a good approach (e.g making it more configurable), hint settings can also optionally be per-project -> this solves multiple issues at once.
The hint can also not simply look at the classpath and try to "do the right thing", since a typical dusty enterprise project has one logging facade but logging bridges to 5+ logging impls - every second lib can use a different impl. So everything might be in the classpath. It likely has to be a user choice set somewhere.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "mbien (via GitHub)" <gi...@apache.org>.
mbien commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2660573162
> We can probably all agree that a library should use a facade and not a specific logger.
sure but in practice it doesn't really matter. For every logging lib a bridge lib exists by now. Logging is a getter with something what holds the log level fields. This can be (luckily) bridged to any other logging impl without having to convince lib authors to use dedicated facades.
The project I am looking at right now uses: jcl-over-slf4j, log4-to-slf4j, jul-to-slf4j and and eclipse logger bridge which maps to slf4j. The "impl" is just yet another bridge, pretending to be a slf4j impl which logs directly to JFR.
> A facility to add/register arbitrary 3rd party logging frameworks/facades..
I wouldn't make this too extensible. Luckily the java community decided at some point to stop developing more logging libs. "Generate -> logger" could offer a list. The hint would also need a few more options.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "matthiasblaesing (via GitHub)" <gi...@apache.org>.
matthiasblaesing commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2657195311
If this is touched, other logging frameworks should also be considered. SLF4J/Log4J2/Logback/commons-logging all can be valid selections for logging. It would be good if this would be per project.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "neilcsmith-net (via GitHub)" <gi...@apache.org>.
neilcsmith-net commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2661568574
I think `System.Logger` should be the default option where we can use it, in preference to JUL. It has the benefit of being in `java.base`.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "mbien (via GitHub)" <gi...@apache.org>.
mbien commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2656790702
parts of this might be already customizable by templates. But I agree there could be likely out-of-the-box improvements made.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2754994131
Would anyone offer suggestions on how to proceed to find reviewer(s) for #8253?
In the OP of this thread, #8240, things that are included in the PR are annotated with `included in #8253`
Hoping this PR can make it into NB26, freeze in less than a month if I'm counting correctly.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2661568068
> > IIUC, JUL can not be a bridge source;
>
> <dependencies>
> ...
Whoa, wow, yeah, OK. That works in many situations where a "sole JUL handler" is OK.
Thanks.
> then it can offer more options for the code gen actions - sure.
Making 3rd party logging a "first class" option in NB needs more that just code gen.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2666910078
Ready for review...
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2662231209
> Opened [#8253](https://github.com/apache/netbeans/pull/8253), DRAFT.
Forgot to mention that the PR is fully functional. (at least that's the idea). It's DRAFT while looking for answers to make sure corner cases are correctly handled.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2661659084
Opened #8253, DRAFT.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] Additional features for working with `Logger`s [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2819431254
The new hint "new fix available: convert string concatenation to Supplier<String>" might be better if it was more like the code that creates a message, but instead uses `String.format()`. Could be a third possible rewrite.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "mbien (via GitHub)" <gi...@apache.org>.
mbien commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2661561782
> IIUC, JUL can not be a bridge source;
```xml
<dependencies>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jul-to-slf4j</artifactId>
<version>2.0.16</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>2.24.3</version>
</dependency>
</dependencies>
```
> If NB want to support code generation for 3rd party logging,
then it can offer more options for the code gen actions - sure.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2658101885
> If this is touched, other logging frameworks should also be considered. SLF4J/Log4J2/Logback/commons-logging all can be valid selections for logging. It would be good if this would be per project.
Before `Java 9` I would 100% agree. But now, doesn't `System.Logger` make all of these selectable at run-time rather than hard-coding?
An anecdote along these lines: There a library project I occasionally work on which used `log4j2`. I finally convinced the owner that `System.Logger` was a superior choice. Wrote some jackpot and converted the code base (with some `sed` assist). Nice that the original log4j config files still worked and the output looked the same.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2658085425
> parts of this might be already customizable by templates. But I agree there could be likely out-of-the-box improvements made.
In addition to stuff mentioned in the OP, there is also stuff in `Tools > Options > Editor > Code Templates`. Is this what you're talking about?
In particular, `log, logb, logbp, logbps, loge, logp, logr, logrb`
These could be copied to `slog, slogb, slogbps, ...`
But I notice that none of these templates have/use `Supplier<String>`; so these templates are often a performance problem. So this probably should be revisited in general rather than copying the old ones.
Also, there's a hint `Inefficient use of string concatenation in logger`.
It has a fix `convert string concatenation to message template`.
```
LOG.log(Level.SEVERE, "message" + a);
```
is converted to
```
LOG.log(Level.SEVERE, "message{0}", a);
```
Could add an additional, probably better, fix: `convert string concatenation to Supplier<String>`.
```
LOG.log(Level.SEVERE, () -> "message" + a);
```
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [I] consider `System.Logger` in related hints/code-generation [netbeans]
Posted by "errael (via GitHub)" <gi...@apache.org>.
errael commented on issue #8240:
URL: https://github.com/apache/netbeans/issues/8240#issuecomment-2660472433
My limited experience with anything other than JUL, is with a library that was developed as part of much larger application. The app used log4j2 and it was used by the library. We can probably all agree that a library should use a facade and not a specific logger. Another selling point of using System.Logger is reducing the library's depency on 3rd party artifacts. I understand that projects have requirements for style/libraries/logging, but I don't understand:
> Only the latter [JUL] could be changed, all others have to integrate with their corresponding ecosystem.
After changing the library (in the example) to System.Logger, and adding the log4j2 bridge to the main app, it integrated fine into the existing ecosystem without any changes to the log4j2 configuration files and produced identical log output.
But that's all beside the point.
A facility to add/register arbitrary 3rd party logging frameworks/facades and their code generation templates/actions and a UI to specify which one to use when NB generates logging code doesn't sound like a bad idea. The most popular logging methods would be provided as reference implementations.
It may be that extending existing capability with JDK's System.Logger is not worth it because of the possibility of re-architecting how NB generates logging.
--
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-unsubscribe@netbeans.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@netbeans.apache.org
For additional commands, e-mail: notifications-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists