Conversation
…4J binding warning Agent-Logs-Url: https://github.com/yeshan333/ApacheJmeter_Schema_Assertion/sessions/2c9fd98d-6c9a-4215-bf0a-be3adfc2083e Co-authored-by: yeshan333 <39296814+yeshan333@users.noreply.github.com>
|
@copilot still have an wanring: |
…ies to test resources Agent-Logs-Url: https://github.com/yeshan333/ApacheJmeter_Schema_Assertion/sessions/dc99b7d5-68bd-446b-830c-136da5304a5c Co-authored-by: yeshan333 <39296814+yeshan333@users.noreply.github.com>
Fixed in a3b2c24. The "package scanning" warnings were caused by |
|
Important Installation incomplete: to start using Gemini Code Assist, please ask the organization owner(s) to visit the Gemini Code Assist Admin Console and sign the Terms of Services. |
The plugin's fat JAR bundles
log4j-slf4j-impl,log4j-core,log4j-api, andlog4j-1.2-api, which conflict with JMeter's own copies at runtime, producingSLF4J: Class path contains multiple SLF4J bindingsandWARN StatusConsoleListener The use of package scanning to locate plugins is deprecatedwarnings.log4j-slf4j-implscope toprovided, matching the existing pattern used fortika-core— both are already supplied by JMeter at runtimelog4j-core,log4j-api, andlog4j-1.2-apiasprovidedscope at version 2.17.2 (matching JMeter 5.5) to prevent their classes and theLog4j2Plugins.datcache file from being bundled in the fat JARlog4j.propertiesfromsrc/main/resources/tosrc/test/resources/to prevent it from interfering with JMeter's logging configuration at runtime