# Which AMPS version to use?

**URL:** <https://community.developer.atlassian.com/t/which-amps-version-to-use/80252>\
**Category:** Jira Server\
**Tags:** amps\
**Created:** [May 23, 2024, 5:57pm UTC](https://community.developer.atlassian.com/t/which-amps-version-to-use/80252 "2024-05-23T17:57:10Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![ViacheslavDobromyslo](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/viacheslavdobromyslo/32/51536_2.png) [@ViacheslavDobromyslo](https://community.developer.atlassian.com/u/ViacheslavDobromyslo)\
**Post date:** [August 31, 2024, 2:50am UTC](https://community.developer.atlassian.com/t/which-amps-version-to-use/80252/15 "2024-08-31T02:50:16Z")

</div>

Thank you, @mkemp ! I will give a try to all the provided tips-and-tricks to make the last AMPS work with the last Jira+Confluence LTS. I have a platform of 10+ plugins with Wired and Web tests to check against.

I made a unified plugin platform with sets of common and product-specific plugins for Jira 9.12.x LTS and Confluence 8.5.x LTS. And it works fine with AMPS 8.11.2 + SDK 8.2.10.

Also, what can you tell about SDK 9.0.2? I see in the Compatibility section that it support only the latest versions:

- Jira Data Center 9.17.1
- Confluence Data Center 9.0.1

Is it backward-compatible with LTSes?

**UPD:**  **SDK 9.0.2 does not work** because of the following error:

```auto
[INFO] Artifact jndi:jndi:pom:1.2.1 is present in the local repository, but cached from a remote repository ID that is unavailable in current build context, verifying that is downloadable from ...
...
Failed to read artifact descriptor for jndi:jndi:jar:1.2.1
Caused by: The following artifacts could not be resolved: jndi:jndi:pom:1.2.1 (present, but unavailable): Could not transfer artifact jndi:jndi:pom:1.2.1 from/to tmatesoft (https://maven.tmatesoft.com/content/repositories/releases/): status code: 403, reason phrase: Forbidden (403)

```

Workaround is here:

> [@Atlassian SDK 9.0.2 Error when using atlas-mvn install](https://community.developer.atlassian.com/t/atlassian-sdk-9-0-2-error-when-using-atlas-mvn-install/82804/5):
>
> If you copy its content in your ~/.m2/repository , or at least the jndi and jta directories, it should work. This does not work. The root cause is that [https://maven.tmatesoft.com/content/repositories/releases/](https://maven.tmatesoft.com/content/repositories/releases/) is not publicly available any longer. It requires login and password to be provided. So you should open the Maven config file atlassian-plugin-sdk-9.0.2/apache-maven-3.9.8/conf/settings.xml and comment out the private Tmatesoft repository: \<settings...\> ... \<profiles\> ... …

There was a support request filed a few days ago in this topic:

> [@Atlassian SDK 9.0.2 Error when using atlas-mvn install](https://community.developer.atlassian.com/t/atlassian-sdk-9-0-2-error-when-using-atlas-mvn-install/82804):
>
> With the new SDK Version 9.0.2, I get the following Error when trying to install the dependencies: [ERROR] Failed to read artifact descriptor for jndi:jndi:jar:1.2.1 [ERROR] Caused by: The following artifacts could not be resolved: jndi:jndi:pom:1.2.1 (present, but unavailable): Could not transfer artifact jndi:jndi:pom:1.2.1 from/to tmatesoft (https://maven.tmatesoft.com/content/repositories/releases/): status code: 403, reason phrase: Forbidden (403) [ERROR] Failed to read artifact de…

---

_[View the full topic](https://community.developer.atlassian.com/t/which-amps-version-to-use/80252)._