4.0-beta-1 💥

First beta release of the 4.0 branch which includes a lot of breaking changes in order to make Plugin POM simple to use and maintain. See this discussion in the developer mailing list for more info. All changes target JENKINS-60474 from #269 by @jtnord

🚀 New features and improvements

• JENKINS-60474 - Libraries that are shipped with jenkins-core now have their dependency versions unconditionally managed from the jenkins-bom. The jenkins-bom and no-jenkins-bom profiles have been removed
  • With this change the libaries used will be correct for a given jenkins.version however this requires a version of Jenkins that was published with the bom (2.195 or higher), or has been explicitly published
  • See here for a list of supported versions
• A quick-build profile has been introduced that disabled things not related to just producing the desired artifacts. This is activated on the command line in the standard maven way (e.g. mvn -P quick-build package)
• Add an extra enforcer rule prevent releases from containing SNAPSHOT versions
• JMH benchmarks are now run by activating the jmh-benchmark directly rather than via a property. (mvn -P jmh-benchmark test)
• Skipping tests using surefire's skipTest property no longer skips other mojos execution.

🚨 Removed

• Deprecated findbugs properties have been removed, use the equivalent spotbugs property (#269) @jtnord
• Support for compiling plugins with java.level < 8 has been removed. The only supported java.level is 8
• Deprecated concurrency property has been removed. use the forkCount surefire option directly from the command line (or pom) (e.g. mvn -DforkCount=4 verify)
• Support for the jgit provider of the release plugin has been removed. Git executable is now required to be installed and available in the PATH
• Automatic re-running of failing tests has been removed.
  • If this is desired it should be set per project by configuring surefire's rerunFailingTestsCount parameter

👻 Maintenance

• Always run the integration tests in this POM (#269) @jtnord