Re: How to suppress JMeter deprecated warning

Tong Sun wrote:
> Had meant to ask for quite a while -- how to suppress JMeter deprecated
> warnings like the following,
>
> "WARN StatusConsoleListener The use of package scanning to locate plugins
> is deprecated and will be removed in a future release
>
> etc? Found a different one BTW at
> https://stackoverflow.com/questions/59733770/how-to-get-rid-of-warning-nashorn-engine-is-planned-to-be-removed-from-a-future
>
> thx
>
>
> On Mon, May 20, 2024 at 12:31 AM Raju Sarkar <[email protected]> wrote:
>
>> Hello sir/mam,
>>
>> ...I'm getting the issue which is mentioned below.../
>>
>> "WARN StatusConsoleListener The use of package scanning to locate plugins
>> is deprecated and will be removed in a future release
>>
>> WARN StatusConsoleListener The use of package scanning to locate plugins is
>> deprecated and will be removed in a future release
>>
>> WARN StatusConsoleListener The use of package scanning to locate plugins is
>> deprecated and will be removed in a future release
>>
>> WARN StatusConsoleListener The use of package scanning to locate plugins is
>> deprecated and will be removed in a future release
>>
If you're not willing to see this warning anymore just remove the 
following bit:

packages="org.apache.jmeter.gui.logging"

from log4j2.xml file (lives in "bin" folder of your JMeter installation, 
see How to Configure JMeter Logging 
<https://www.blazemeter.com/blog/jmeter-logging> article for more details)

after restart you won't see this warning anymore.

See

However it will result into some side-effects like other warnings, not 
working log viewer, etc. so you will need to rebuild JMeter 
<https://jmeter.apache.org/building.html> like it's described here 
<https://stackoverflow.com/questions/54426102/configure-gradle-with-annotationprocessor-and-log4j2-pluginprocessor>