- Client version updated on 5.2.11, by @HardNorth
- Client version updated on 5.2.5, by @HardNorth
client-java
andlog4j-core
dependencies marked ascompileOnly
to force users specify their own dependencies, by @HardNorth
- Client version updated on 5.2.4, by @HardNorth
commons-model
dependency to rely onclient-java
exclusions in security fixes, by @HardNorth
- Client version updated on 5.2.0, by @HardNorth
- Client version updated on 5.1.22, by @HardNorth
- Plugin location by annotation processor, by @valfirst
- Client version updated on 5.1.21, by @HardNorth
- Client version updated on 5.1.16, by @HardNorth
- Log4j 1.2 support, since it's extremely vulnerable, by @HardNorth
- Logging issues skip, by @HardNorth
- Client version updated on 5.1.11, by @HardNorth
- Log4j version updated on 2.17.2, by @HardNorth
- A bug with wrong object casting, by @jusski
- Client version updated on 5.1.4
- Log4j version updated on 2.17.1 due to vulnerability
- Log4j version updated on 2.17.0 due to critical vulnerability
- Log4j version updated on 2.16.0 due to critical vulnerability
- Log4j version updated on 2.15.0 due to critical vulnerability
- Version promoted to stable release
- Client version updated on 5.1.0
- Client version updated on 5.1.0-RC-12
- bumping up client version
- Workarounded: A multi-threaded bug in Log4j 1.2 log formatting. When a log line mixes with other nearest log lines. This fix affects logger performance, so it's a common recommendation to avoid using Log4j 1.2
- bumping up client version
- reportportal/agent-java-testNG#8 - Java agent sends duplicate log entries to Report Portal