Container won't start (atlassian-plugin-sdk-rpm obsoleted)

[stefanvogel]

2025-02-17 09:41:13 [ERROR] Failed to execute goal com.atlassian.maven.plugins:jira-maven-plugin:8.0.2:run (default-cli) on project myartifact: Execution default-cli of goal com.atlassian.maven.plugins:jira-maven-plugin:8.0.2:run failed: java.io.FileNotFoundException: https://marketplace.atlassian.com/rest/1.0/plugins/atlassian-plugin-sdk-rpm -> [Help 1]
2025-02-17 09:41:13 [ERROR] 
2025-02-17 09:41:13 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2025-02-17 09:41:13 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2025-02-17 09:41:13 [ERROR] 
2025-02-17 09:41:13 [ERROR] For more information about the errors and possible solutions, please read the following articles:
2025-02-17 09:41:13 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
2025-02-17 09:41:13

Using LATEST.

docker run -dit -p 2990:2990 --name jira-python addono/jira-software-standalone --version 8.17.1

Occurs since last week Friday, all of a sudden.

My guess is that https://marketplace.atlassian.com/rest/1.0/plugins/atlassian-plugin-sdk-rpm does no longer exist, i.e. has been renamed and needs to be changed to atlassian-plugin-sdk-rpm-obsolete

Edit: The problem seems to originate from docker-atlassian-sdk already (https://github.com/Addono/docker-atlassian-sdk/blob/master/Dockerfile), where the same error happens e.g. with command
docker run -it -p 2990:2990 addono/atlassian-sdk atlas-run-standalone --product jira

[stefanvogel]

Hi @Addono, could you take a look please.

[Addono]

Hey! Thanks for the report.

To be honest, I've not been too active in Jira development works these days. I can take a quick look, but to be frank it's not really high on my priority list to sink a lot of time into it.

Happy to take contributions though.

---

I've been looking into it a bit, and don't see an obvious fix. You are right that it's reproducible in the upstream image.

My guess is that it's that SDK toolkit which is the root cause, as probably that one has the Maven dependency.

In the upstream image, we just try to install the latest version of Atlassian Plugin SDK from some Artifactory instance. Rebuilding that image in an attempt to pull in a newer version still yields the same version of the Atlassian Plugin SDK, so seems like it's not being updated there anymore.

I'll update the installation method for Atlassian Plugin SDK to the one which is currently recommended, that will get us v9.1.1 of Atlassian Plugin SDK.

But, then there's still things not working immediately on this part of the project again. So partial fix is there. Not sure when I'll have time to look into this again.