Refresh plugin

[basil]

Updates all dependencies to the latest version, including adapting to recent Maven plugin API changes. Since Kohsuke's parent POM is no longer maintained and the Jenkins parent POM publishes to the Jenkins Artifactory rather than Maven Central, I have chosen to remove any parent POM from this project. While this does entail a little duplication, it simplifies the management of this non-standard component by only pulling in exactly what we need. The ugliness of a solution that duplicates the code merely mirrors the ugliness of the deployment setup and GitHub organization of this repository, which does not follow our standard conventions.

Testing done

I ensured that Javadocs could be built by running (locally) mvn clean verify -Pcloudbees-release -Dgpg.skip on both Java 8 and Java 11.

I tested this on Java 19 with a Jenkins core build and verified that the generated license information was the same before and after this PR. Note that to adapt to Maven API changes the core build needed this patch:

@@ -565,7 +565,11 @@ THE SOFTWARE.
                 // add Winstone since we are bundling it.
                 def d = project.dependencies.find { it.artifactId=="winstone" };
                 def a = mojo.artifactFactory.createProjectArtifact(d.groupId,d.artifactId,d.version);
-                def p = mojo.projectBuilder.buildFromRepository(a, project.getRemoteArtifactRepositories(), mojo.localRepository)
+                def buildingRequest = new org.apache.maven.project.DefaultProjectBuildingRequest(mojo.session.projectBuildingRequest)
+                buildingRequest.remoteRepositories = project.remoteArtifactRepositories
+                buildingRequest.localRepository = mojo.localRepository
+                buildingRequest.processPlugins = false // improve performance
+                def p = mojo.projectBuilder.build(a, buildingRequest).project
                 models.put(a,p);

CC @jglick

[jglick]

Looks good. Let me see if I can cut a release without tricks…

[jglick]

I suspect we could add anything needed (like GPG signing) to the standard release profile, but this is fine too.

[jglick]

I do not think we still need this—can assume that releases run on 11 (or newer).

[jglick]

👍

[jglick]

Nope:

[INFO] [ERROR] Rule failure while trying to close staging repository with ID "comcloudbees-1211".
[INFO] [ERROR] 
[INFO] [ERROR] Nexus Staging Rules Failure Report
[INFO] [ERROR] ==================================
[INFO] [ERROR] 
[INFO] [ERROR] Repository "comcloudbees-1211" failures
[INFO] [ERROR]   Rule "pom-staging" failures
[INFO] [ERROR]     * Invalid POM: /com/cloudbees/maven-license-plugin/1.13/maven-license-plugin-1.13.pom: Project description missing, License information missing, Developer information missing

Probably things that came from the parent. I will try to fix.

[jglick]

After some trial & error, managed to get https://github.com/cloudbees/maven-license-plugin/releases/tag/maven-license-plugin-1.15 released. https://gist.github.com/jglick/b4ece94b38f139a66d3333f7cc925099 FTR