Announcing AMPS 8.0.0



AMPS version 8.0.0 is now available.

This release has some major changes, including:

Full details will be found in the Release Notes (available later this week)

AMPS 8.0.0 is not compatible with the Atlassian Plugin SDK version 6.x and earlier. If you’d like to use AMPS 8.0.0 with the Atlassian Plugin SDK, please wait for the Atlassian Plugin SDK version 8.0.0 release coming soon. Announcements will be posted in the Developer Community Forums.


Hi Melissa,

We got Atlassian Plugin SDK 8 this morning via our package manager, we tried updating to AMPS 8 too but this broke all of our maven builds with the following output:

[ERROR] Invalid Atlassian maven plugin detected: maven-compiler-plugin

It seems a bit odd for the SDK to be complaining about non-Atlassian plugins? I could understand if the error was complaining about specific versions, but we should still be able to use standard maven artifacts right?

We might have jumped the gun, perhaps the above is addressed in the upcoming release notes.

Any tips? Cheers!


The Atlassian Plugin SDK version 8.0.4 is now available and can be downloaded from here. AMPS 8.0.0 is compatible with this release.


@abhayani are there any release notes for this new SDK? Our builds are broken with AMPS 8/Plugin SDK 8, see my previous comment for the error we are getting.


Hi @reece thanks for pointing this out. This is a bug and has been detailed in

We aim to get this fixed sometime next week. In the meantime you can potentially call AMPS commands directly as detailed in the above ticket.


Some release notes links are dead, for example

Correct links:


The deprecated atlas-cli and fastdev were finally removed, right?

Is there a task to also upgrade/clean up the documentation, for example: ?

I also still see an atlas-cli.bat in the atlassian-plugin-sdk-8.0.4 (trying to use AMPS 8.0.0).


I’m having issue with integration tests after upgrade.

Before the update I was running specific test groups with command like atlas-integration-test -DtestGroups=jira-current and it was running smoothly.
After the update and manually fixing atlas-integration-test script I now see the following output:

Executing: /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.5.4/bin/mvn com.atlassian.maven.plugins:amps-maven-plugin:8.0.0:integration-test -gs /usr/local/Cellar/atlassian-plugin-sdk/6.2.14/libexec/apache-maven-3.5.4/conf/settings.xml -DtestGroups=jira-current
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
[INFO] Scanning for projects...
[INFO] --------------------< ru.mail.jira.plugins:groovy >---------------------
[INFO] Building MyGroovy 1.17.9
[INFO] --------------------------[ atlassian-plugin ]--------------------------
[INFO] --- amps-maven-plugin:8.0.0:integration-test (default-cli) @ groovy ---
[INFO] No integration tests found
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.594 s
[INFO] Finished at: 2019-02-15T11:44:54+03:00
[INFO] ------------------------------------------------------------------------

Did something change that I’m missing?
You can check the pom file here:

Atlas-integration-test ignoring products in pom.xml on version 8.0.0+

Maven repo doesn’t have the maven-jira-plugin:8.0.0

Unresolveable build extension: Plugin com.atlassian.maven.plugins:maven-jira-plugin:8.0.0 or one of its dependencies could not be resolved: Could not find artifact com.atlassian.maven.plugins:maven-jira-plugin:jar:8.0.0 in atlassian-public (


Based on, maven-jira-plugin is changed to jira-maven-plugin for v8.x.

Hope this helps.


Thanks for the response. Can the documentation be updated to reflect those changes:


Hey @a.belostotskiy, have you found a solution for this problem? I’ve just got stuck at the same point :frowning:




@a.belostotskiy and @vpelizza we realised there is a bug with the integration tests. A Jira ticket has been raised at Please feel free to vote / watch the issue for updates.


That ticket seems to be about maven command naming.
We’re having issue with tests not being found after workaround, which seems to be a different issue.

Atlas-integration-test ignoring products in pom.xml on version 8.0.0+

Could someone confirm this (if atlas-cli and fastdev have been removed) please?

atlas-cli still exists but is using maven-amps-dispatcher-plugin instead of amps-dispatcher-maven-plugin, which means it doesn’t work.