[
https://issues.apache.org/jira/browse/LOG4J2-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17467424#comment-17467424
]
Gotthard Witsch commented on LOG4J2-3267:
-----------------------------------------
Thanks for implementing this so fast (y)
> Getting public access to
> org.apache.logging.log4j.core.tools.Generate#generate method for automated
> code generation
> -------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3267
> URL: https://issues.apache.org/jira/browse/LOG4J2-3267
> Project: Log4j 2
> Issue Type: Wish
> Components: Core
> Affects Versions: 2.17.0
> Reporter: Gotthard Witsch
> Assignee: Remko Popma
> Priority: Minor
> Fix For: 2.17.2
>
>
> Hi devs,
> I'd like to automate the creation of a custom logger with gradle.
> Sticking to the documentation i've tried to use
> org.apache.logging.log4j.core.tools.ExtendedLoggerGenerator as mentioned in
> [Log4j – Custom Log Levels
> (apache.org)|https://logging.apache.org/log4j/2.x/manual/customloglevels.html#CustomLoggers]
> Unfortunately the output can only be consumed from console, making it very
> hard for automation.
> Investigating the implemenation led me to
> org.apache.logging.log4j.core.tools.Generate.generate.
> Unfortunately the required method is package private.
> Therefore it would be helpful to change the generate-method's visibility to
> public to gain access in gradle scripts.
> {code:java}
> static void generate(final String[] args, final Type type, final PrintStream
> printStream) {code}
> Is there any chance of changing this? Or what was the intention to keep it
> package-private?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
