I have got information from Ewelina Wilkosz that the plugin is no longer maintained by Praqma.
CC Igor Kostenko and Marcos Bento who are listed in Repository permission updater

I also dropped the default assignee of the component. Please let me know whom to set the new lead of the component in JIRA

The plugin and the library are being maintained by the tool vendor. The plugin has no real tests. Although I have a license for PRQA, it would take a while to setup the test projects, etc.
So far me and Jesse Glick are not going to spend time on fixing this plugin unless there is a community feedback.

Igor Kostenko Marcos Bento Please let us know if you need any advice.

Igor Kostenko Marcos Bento ping

I have raised the question to the tool vendor 10 days ago. JEP-200 maintainers are not going to work on it so far

Oleg Nenashev,

So,We cant able to work PRQA in jenkins?

Thanks,

Priyanga

Priyanga G Please see https://jenkins.io/blog/2018/03/15/jep-200-lts/ . This blogpost offers troubleshooting guidelines and some workaround options. You won't be able to use this plugin with Jenkins 2.102+ if you do not construct workaround class filter settings.

We were unable to get a response from the plugin maintainers even after reaching out to PRQA directly. If you suffer from this issue, please submit a support ticket to PRQA.

Oleg Nenashev,

Thank you for reply sir.

I am using Jenkins 2.111 version.If I downgrade the Jenkins version.It will work??

Yes, it will

Thank you sir.

This issue is fixed in PRQA Jenkins plugin 3.0.1.

Marcos Bento there is no source code in https://github.com/jenkinsci/prqa-plugin . Could you please push it?

The source code has been pushed.

thanks!