ppkarwasz closed issue #2131: Split CLI commands from `log4j-1.2-api` and
`log4j-core`
URL: https://github.com/apache/logging-log4j2/issues/2131
--
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
ppkarwasz commented on issue #2131:
URL:
https://github.com/apache/logging-log4j2/issues/2131#issuecomment-2072312141
Closed in #2435
--
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
vy commented on issue #2131:
URL:
https://github.com/apache/logging-log4j2/issues/2131#issuecomment-1871890651
@ppkarwasz, if we are gonna totally remove it in `3.x`, I think we can lay
down the separate artifact to `2.x` to rest in peace.
--
This is an automated message from the Apache
ppkarwasz commented on issue #2131:
URL:
https://github.com/apache/logging-log4j2/issues/2131#issuecomment-1871883730
@vy,
I meant to transfer the code that **used** Picocli to a new artifact and add
`info.picocli:picocli` as a dependency.
Actually I have [a branch for this
vy commented on issue #2131:
URL:
https://github.com/apache/logging-log4j2/issues/2131#issuecomment-1871879604
I support the proposed `log4j-1.2-api` changes.
> Log4j Core contains ... an old copy of [remkop/picocli](/remkop/picocli).
This should also be ... transferred to a new
ppkarwasz opened a new issue, #2131:
URL: https://github.com/apache/logging-log4j2/issues/2131
There are a couple of CLI commands in the current 2.x artifacts. Their code
is not used by other Log4j components.
### `log4j-1.2-api`
`log4j-1.2-api` contains a
