Issue #39: Upgrade plugins and dependencies

[reckart]

What's in the PR

• build-groovy-version 4.0.15 -> 4.0.21
• build-ant-version 1.10.13 -> 1.10.14
• build-asciidoctorj-pdf-version 2.3.9 -> 2.3.15
• versions-maven-plugin 2.16.2 -> 2.18.0
• maven-clean-plugin 3.3.2 -> 3.5.0
• maven-install-plugin 3.1.2 -> 3.1.4
• maven-compiler-plugin 3.13.0 -> 3.14.0
• maven-jar-plugin 3.4.1 -> 3.4.2
• maven-javadoc-plugin 3.6.3 -> 3.11.2
• maven-release-plugin 3.0.1 -> 3.1.1
• maven-surefire-plugin 3.2.5 -> 3.5.3
• maven-deploy-plugin 3.1.2 -> 3.1.4
• maven-dependency-plugin 3.6.1 -> 3.8.1
• maven-pmd-plugin 3.22.0 -> 3.27.0
• jacoco-maven-plugin 0.8.12 -> 0.8.13
• maven-remote-resources-plugin 3.2.0 -> 3.3.0
• maven-enforcer-plugin 3.4.1 -> 3.6.0
• maven-gpg-plugin 3.2.4 -> 3.2.8
• build-helper-maven-plugin 3.5.0 -> 3.6.1
• asciidoctor-maven-plugin 3.0.0 -> 3.2.0
• spotbugs-maven-plugin 4.8.5.0 -> 4.9.3.2

How to test manually

• No specific test procedure

Automatic testing

• PR includes unit tests

Documentation

• PR updates documentation

[reckart]

I guess what I will (have to do) is decouple INCEpTION from the DKPro Parent POM since it is currently the odd-one out.

Or alternatively split the DKPro Parent POM into two, one being the "root parent" which sets up all the plugins and stuff except the maven central plugin and then one that inherits from that one and adds the maven central plugin. In order to publish that whole bunch, I think I'd then have to add the maven central plugin to .mvn/extensions.xml in the parent POM repo so it can take effect even without being declared in the "root" POM.

[reckart]

@rzo1 I believe you could also for the time being just add the maven central plugin to JWPL without making any change to the DKPro Parent POM at all - that would at least remove it as a blocker for you.

[reckart]

Btw, I'd recommend setting a deploymentName in the plugin configuration since otherwise all deployments show up as "Deployment" in the publishing UI and you can only distinguish them by ID or timestamp.

[reckart]

The INCEpTION bundle didn't even validate on Maven Central - failing with

Failed to process deployment: Error on building manifests: No Archiver found for the stream signature Details: No Archiver found for the stream signature

No idea what it's problem is...

[rzo1]

I believe you could also for the time being just add the maven central plugin to JWPL without making any change to the DKPro Parent POM at all - that would at least remove it as a blocker for you.

Yep. Let's do that.