Plugin size is too high and contains unused dependencies

[nfalco79]

What feature do you want to see added?

When I implemented the PR #29 as artifact of the build I get an HPI of 31Mb.
When I see inside HPI I'm surprised that there was a lot of dependencies that sound strange inside a plugin.
Just and example the whole spring framework (included with commit 99df204), jetty embedded server and so on.
Also it the could works thanks to the jenkins plugin classloading it's a problem if all plugin do that. Because of memory, problem at runtime when comunicate with other plugins same class loaded from different classloader, time of startup and so on.

Upstream changes

No response

[MarkEWaite]

This is now a blocking bug. Jenkins 2.434 and later will refuse to load a plugin that includes the Jenkins test harness. Jenkins 2.434 includes the pull request:

• Refuse to load the Jenkins test harness in production jenkins#8714

The Jenkins test harness causes unexpected failures when it is included in a Jenkins plugin. Refer to the following issue reports for examples:

• https://issues.jenkins.io/browse/JENKINS-65650
• https://issues.jenkins.io/browse/JENKINS-66060
• https://issues.jenkins.io/browse/JENKINS-72353

This plugin will be unusable with Jenkins releases after 2.434 until a new release is created that includes the changes in:

• Fix #30 Remove the amount of dependencies to only required, use just one JSON parser preferring that one that comes from Jenkins core. #36

Other changes may be required, but the changes in that pull request are certainly required.