[ERROR] Failed to execute goal com.atlassian.maven.plugins:amps-maven-plugin:8.1.2:run-standalone (default-cli) on project standalone-pom:
Unable to find/resolve artifact.: Failed to read artifact descriptor for com.atlassian.synchrony:synchrony-proxy:war:4.0.7:
Failure to find com.atlassian.platform.dependencies:platform-deps:pom:7.1.10 in https://maven.atlassian.com/repository/public
was cached in the local repository, resolution will not be reattempted until the update interval of atlassian-public has elapsed
or updates are forced -> [Help 1]
Steps Taken:
Verified that the Maven repository URL (https://maven.atlassian.com/repository/public) is not accessible.
Ensured that my settings.xml file is configured correctly with Atlassian’s public repositories.
Cleared the local .m2/repository cache and retried with the -U flag to force dependency updates:
It seems the dependency com.atlassian.platform.dependencies:platform-deps:pom:7.1.10 is missing or inaccessible from Atlassian’s public Maven repository.
This issue may be related to recent changes in the Maven repository or artifact configurations.
Yes, I had the same thing, I can’t run any plugins.
There was a dependency download that broke my entire dev environment.
I raised a Critical Bug with Atlassian, this happened to me about 8 hours ago. But the Atlassian maven commit probably happened well before this time.
Waiting for Atlassian to fix so I can continue my work.
This was the download that broke the environment.
[INFO] Configured Artifact: com.atlassian.synchrony:synchrony-proxy:4.0.7:war
Downloading from atlassian-public: https://maven.atlassian.com/repository/public/com/atlassian/synchrony/synchrony-proxy/4.0.7/synchrony-proxy-4.0.7.pom
Downloaded from atlassian-public: https://maven.atlassian.com/repository/public/com/atlassian/synchrony/synchrony-proxy/4.0.7/synchrony-proxy-4.0.7.pom (32 kB at 8.7 kB/s)
Downloading from atlassian-public: https://maven.atlassian.com/repository/public/com/atlassian/platform/dependencies/platform-system-classpath/7.1.10/platform-system-classpath-7.1.10.pom
Downloading from atlassian-plugin-sdk: file:///C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7/repository/com/atlassian/platform/dependencies/platform-system-classpath/7.1.10/platform-system-classpath-7.1.10.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/atlassian/platform/dependencies/platform-system-classpath/7.1.10/platform-system-classpath-7.1.10.pom
Downloading from atlassian-public: https://maven.atlassian.com/repository/public/com/atlassian/platform/dependencies/platform-test-resources/7.1.10/platform-test-resources-7.1.10.pom
Downloading from atlassian-plugin-sdk: file:///C:\Applications\Atlassian\atlassian-plugin-sdk-8.2.7/repository/com/atlassian/platform/dependencies/platform-test-resources/7.1.10/platform-test-resources-7.1.10.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/atlassian/platform/dependencies/platform-test-resources/7.1.10/platform-test-resources-7.1.10.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 39.346 s
[INFO] Finished at: 2024-11-29T16:21:38+11:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:amps-dispatcher-maven-plugin:8.1.2:debug (default-cli) on project easy-forums: Unable to find/resolve artifact.: Failed to read artifact descriptor for com.atlassian.synchrony:synchrony-proxy:war:4.0.7: Could not find artifact com.atlassian.platform.dependencies:platform-system-classpath:pom:7.1.10 in atlassian-public (https://maven.atlassian.com/repository/public) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
I would suggest that anyone with this issue raise a bug. This is critical, and it is the first time in my 15 years of development on this platform that it has been broken.
This issue should be resolved now, so please go ahead and test the build works. We’ve updated our internal process a bit so if there are outages in our maven repos we’ll raise internally as an incident to avoid this happening again. But, please note that the team is based in Sydney (currently UTC+11) so unless it’s a major outage affecting multiple Partners and apps, it will only be worked on during business hours.