Adaptavist moved Nexus repository from nexus.adaptavist.com to nexus.adaptavist.net

Jira Development Jira Data Center
, ,
1

Today I decided to rebuild one plugin based on ScriptRunner and I was confused by the following error:

Non-resolvable parent POM for com.example.jira:jira-scriptrunner-scripts:1.0-SNAPSHOT: Failure to transfer com.adaptavist.pom:scriptrunner-jira-standard:pom:62 from https://nexus.adaptavist.com/content/repositories/external was cached in the local repository, resolution will not be reattempted until the update interval of adaptavist-external has elapsed or updates are forced.

I even tried to open it in a browser and got “domain name not found” error. Then I tried to check the official documentation with no luck. I even thought that Adaptavist decided to close their repository from developers…

Eventually, I found the reason in the repository with sample plugins based on ScriptRunner for atlassian products - Bitbucket

- <url>https://nexus.adaptavist.com/content/repositories/external</url>
+ <url>https://nexus.adaptavist.net/content/repositories/external</url>

Now the repository definition in pom.xml should be like this:

<repository>
  <id>adaptavist-external</id>
  <url>https://nexus.adaptavist.net/content/repositories/external</url>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
  <releases>
    <enabled>true</enabled>
    <checksumPolicy>fail</checksumPolicy>
  </releases>
</repository>
2 Likes
2

This was a bit of oversight on our end, we’re slowly migrating some services away from our .com TLD onto .net

We hadn’t initially considered external consumers of Nexus, but we have now updated our public examples to point at the new TLD.

4 Likes