tree 763ac92f650ecab0f4ede7a8c49c7df5ae1e18da
parent 019454f1a4154dba44b4e9b54b7a248dfcb69b49
author Lari Hotari <lhotari@users.noreply.github.com> 1623828820 +0300
committer GitHub <noreply@github.com> 1623828820 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgyalUCRBK7hj4Ov3rIwAA6ZAIADU/DT+RHDpBhUlnK9TsWv0Y
 mHb95/LSl5x7GO2wYxaj1n7lZWAUAAjjQHSm6G3S2OFW9OggjTaKHA6O7pv+SiJg
 UeQ6XKiojtsxTPxPyTBFTR7+HcBJfY20YXvwp2fviPRjc1/pebCGCZ8EXFFWJI9X
 hz9gHBqtRSMfQjDa1LqzfU4LwD4oJH7D0e+98Gj0IL7X4jUnhFRjjIp0FhMjkXvU
 slJCDujpAShIyyI7DxAKOzz7qlD1tX5Tu/4bq9pNofrIsfh7/RS7JGeQDgqI5dWD
 VBkemxvPC3Ugt7RN/ZgINBzjUbnff2+aBZky+I66jc8ZDVAxlkRO7RAHJGO3+Mw=
 =nCt2
 -----END PGP SIGNATURE-----
 

Pulsar Log4j2 Appender: allow configuration of the client (#17)

Fixes #15, #16

### Motivation

When Pulsar security is enabled, the current implementation is unusable. This PR also covers the feature request #16 to allow configuring most client and producer configuration properties.
The issue #15 makes the Pulsar Log4j2 Appender unusable in many use cases. This PR fixes the issue by removing the hard coded producer name.
The current build for Pulsar Log4j2 Appender is broken. This PR fixes the build by properly configuring Log4j2 plugin annotation processor for the maven build. There were broken tests which were unnecessary and testing Log4j2 internals instead of the appender. Those tests have been removed

### Modifications

- add support for configuring Pulsar client and producer configuration properties (#16)
- fix maven build (Log4j2 plugin annotation processor)
- remove broken tests which were unnecessary
- remove the hard coded producer name which prevented using the appender in many use cases (#15)