pin go-offline to 3.9.0

[darinpope]

#6957 has failed numerous times. After some help from Claude, it appears that when you invoke a plugin by goal-prefix on the CLI like this, Maven resolves the latest released version. It does not reliably honor the version for a direct prefix invocation.

maven-dependency-plugin 3.11.0 was released 2026-05-24. The last successful build of org.jenkins-ci:jenkins was in January 2026, when 3.9.0 was the available version, which is the pinned version in the parent POM.

Going to test to see if pinning to 3.9.0 fixes the issue or not.

Testing done

none

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[dduportal]

After a bit or playing around, the error comes from the 3.11.0 release (3.10.0 works) and comes from apache/maven-dependency-plugin#1603.

The error is:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.11.0:go-offline (default-cli) on project parent: The following artifacts could not be resolved: org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 (absent): org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 was not found in https://repo.jenkins-ci.org/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of repo.jenkins-ci.org has elapsed or updates are forced -> [Help 1]

This plugin comes from https://github.com/jenkinsci/jenkins/blob/490402c541774a087eab605a07e6f11f8cb052e0/pom.xml#L223-L226 which version is specified in https://github.com/jenkinsci/pom/blob/45bc61c117083efcaf1074383c0d210e21941c4d/pom.xml#L127