Marketplace API shutdown affecting AMPS

Atlassian Marketplace has shutdown their V1 REST API. This will mean that you’ll likely see this error message if you’re working on DC. AMPS will not continue the command because it failed to check for an update.

[ERROR] Failed to execute goal com.atlassian.maven.plugins:amps-maven-plugin:9.1.1:debug (default-cli) on project quickreload: Execution default-cli of goal com.atlassian.maven.plugins:amps-maven-plugin:9.1.1:debug failed: java.io.FileNotFoundException: https://marketplace.atlassian.com/rest/1.0/plugins/atlassian-plugin-sdk-tgz -> [Help 1]

This is fixed in version 9.1.11 and that can be set in your top-level pom.xml like so:

<pluginManagement>
        <plugins>
            <plugin>
                <groupId>com.atlassian.maven.plugins</groupId>
                <artifactId>amps-maven-plugin</artifactId>
                <version>9.1.11</version>
            </plugin>
        </plugins>
</pluginManagement>

The other alternative is to set skipAllPrompts to true. I don’t recommend this so you that continue to get update prompts when a new version of AMPS is released which is how bugfixes and forward compatibility with products is rolled out.

You’d do it like so:

<pluginManagement>
        <plugins>
            <plugin>
                <groupId>com.atlassian.maven.plugins</groupId>
                <artifactId>amps-maven-plugin</artifactId>
                <configuration>
                    <skipAllPrompts>true</skipAllPrompts>
                </configuration>
            </plugin>
        </plugins>
</pluginManagement>
5 Likes

Hey @mkemp,
are you sure, that version 9.1.11 really has the bugfix included?

At least the decompiled code still shows the old endpoint, right?

Cheers,
Marcel

2 Likes

I was just about to do the Confluence Hello World Tutorial and ran into this.
I just had to change the amps.version in the properties section:

<project>
  ...
  <properties>
  ...
    <amps.version>9.1.11</amps.version>
  ...  
  </properties>

</project>

Cheers,
Christian

2 Likes

Yes, sorry, I should clarify it’s not entirely resolved and we’re working on that internally (sorry). When I learn more I’ll share here.

Please let us know if you have more problems (with these kind of things we can be inadvertantly blind to certain setups).

1 Like