Missing Jenkins Repository for Jira 9.12.x Plugin Build

gist-jenkins-dependency-issue.md

Missing Jenkins Repository for Jira 9.12.x Plugin Build

Problem

When building an Atlassian Jira plugin against Jira 9.12.x, Maven fails with:

Failed to read artifact descriptor for commons-httpclient:commons-httpclient:jar:3.1-jenkins-3
Caused by: The following artifacts could not be resolved: org.jenkins-ci:jenkins:pom:1.39

Root Cause

Jira 9.12.x introduced a transitive dependency on commons-httpclient:3.1-jenkins-3 — a custom Jenkins build of the Apache Commons HttpClient library.

This artifact and its parent POM (org.jenkins-ci:jenkins:1.39) are hosted in the Jenkins repository, which is not configured by default in Atlassian Plugin SDK.

Solution

Step 1: Add Jenkins Repository to pom.xml

<repositories>
    <repository>
        <id>jenkins-releases</id>
        <url>https://repo.jenkins-ci.org/releases/</url>
    </repository>
</repositories>

Step 2: Exclude Jenkins Repository from Maven Central Mirror

If you have a mirror with mirrorOf=* in your settings.xml, add the exclusion:

<!-- Before -->
<mirrorOf>*,!atlassian-local,!atlassian-public</mirrorOf>

<!-- After -->
<mirrorOf>*,!atlassian-local,!atlassian-public,!jenkins-releases</mirrorOf>

Step 3: Force Update Cached Failures

Maven caches failed download attempts. Force an update:

atlas-mvn clean package -U

Why This Happens

The dependency chain looks like this:

jira-api:9.12.30
  └── some-atlassian-lib
        └── commons-httpclient:3.1-jenkins-3
              └── org.jenkins-ci:jenkins:1.39 (parent POM)

The 3.1-jenkins-3 version is a patched version maintained by Jenkins CI, not available in Maven Central or Atlassian repositories.

Verification

After applying the fix:

atlas-mvn clean package -U

Should complete with BUILD SUCCESS.

Affected Jira Versions

This issue affects Jira versions 9.12.x and later that include the Jenkins-patched httpclient.