Running atlas-create-jira-plugin fails with "Unknown host maven.atlassian.com"
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When referring to Create a HelloWorld Plugin Project and running atlas-create-jira-plugin, it fails with the following error
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-jira-plugin:6.2.11:create (default-cli) on project standalone-pom: Execution default-cli of goal com.atlassian.maven.plugins:maven-jira-plugin:6.2.11:create failed: Plugin com.atlassian.maven.plugins:maven-jira-plugin:6.2.11 or one of its dependencies could not be resolved: Failed to collect dependencies at com.atlassian.maven.plugins:maven-jira-plugin:jar:6.2.11 -> com.atlassian.maven.archetypes:jira-plugin-archetype:jar:6.2.11 -> org.twdata.maven:mojo-executor:jar:1.5.2 -> org.apache.maven:maven-artifact:jar:3.2.1 -> org.codehaus.plexus:plexus-utils:jar:3.0.17: Failed to read artifact descriptor for org.codehaus.plexus:plexus-utils:jar:3.0.17: Could not transfer artifact org.codehaus.plexus:plexus-utils:pom:3.0.17 from/to atlassian-public (https://maven.atlassian.com/repository/public): maven.atlassian.com: Unknown host maven.atlassian.com -> [Help 1]
Diagnosis
- Already checked https://cwiki.apache.org//confluence/display/MAVEN/PluginResolutionException to overcome Maven https issue
- Already referred to https://developer.atlassian.com/docs/advanced-topics/working-with-maven/atlassian-maven-repositories and updated the repo URLs
- Previous packages successfully loaded
Downloading: https://packages.atlassian.com/maven/repository/public/org/codehaus/plexus/plexus-compo\\ nent-api/1.0-alpha-16/plexus-component-api-1.0-alpha-16.pom
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-\\ 16/plexus-component-api-1.0-alpha-16.pom
Downloading: https://packages.atlassian.com/maven/repository/public/org/codehaus/plexus/plexus-utils\\ /1.0.4/plexus-utils-1.0.4.pom
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/1.0.4/plexus-utils\\ -1.0.4.pom
Downloading: https://packages.atlassian.com/maven/repository/public/org/codehaus/plexus/plexus-conta\\ iner-default/1.0-alpha-8/plexus-container-default-1.0-alpha-8.pom
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-container-default/1.0-al\\ pha-8/plexus-container-default-1.0-alpha-8.pom
Cause
Proxy configuration causing issues
Workaround
- Add proxy configuration to .m2/settings.xml
- If proxy uses NTLM authentication, ensure that it is enabled for Maven following this instructions: https://codepen.io/ugbandula/post/how-to-configure-maven-to-work-with-ntlm-proxies
Last modified on Sep 19, 2017
Powered by Confluence and Scroll Viewport.