hostname in certificate didn't match: <maven.atlassian.com>

[KL Kumar]

Hello All,

I have developed a custom jira plugin and all these days it is working perfectly without any issues. Now we have a new enhancement requirement to it and trying to rebuild the existing code in my local machine. Now it throws me build errors (hostname in certificate didn't match). This is a server version.

Below are the properties from my pom.

<properties>
  <jira.version>8.0.2</jira.version>
  <amps.version>8.0.0</amps.version>
  <plugin.testrunner.version>1.2.3</plugin.testrunner.version>
  <atlassian.spring.scanner.version>1.2.6</atlassian.spring.scanner.version>
  <testkit.version>6.3.11</testkit.version>
  <quick.reload.version>3.0.0</quick.reload.version>
  <maven.compiler.source>1.8</maven.compiler.source>
  <maven.compiler.target>1.8</maven.compiler.target>
  <atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>
  <maven.test.skip>true</maven.test.skip>
</properties>

Can someone help me with the solution?

[ERROR] Unresolveable build extension: Plugin com.atlassian.maven.plugins:maven-jira-plugin:8.0.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for com.atlassian.maven.plugins:maven-jira-plugin:jar:8.0.0: Could not transfer artifact com.atlassian.maven.plugins:maven-jira-plugin:pom:8.0.0 from/to atlassian-public (https://maven.atlassian.com/repository/public): hostname in certificate didn't match: <maven.atlassian.com> != <*.services.atlassian.com> OR <*.services.atlassian.com> OR <services.atlassian.com> -> [Help 2]

 Thanks!

Kumar

[Roman Bubiakin _Wombats Corp_]

Updating sdk to the latest solve the problem

https://marketplace.atlassian.com/apps/1210950/atlassian-plugin-sdk-windows/version-history

Actually the problem is in outdated maven version packed into atlassian-sdk, nevertheless fully update sdk is always a good idea.

[Sodiq Fagbola]

I updated the plugin to the latest version and still have the same problem

[Takayuki Hirota]

A few days ago, I encountered same problem with JDK 1.8.0_131 and resolved with JDK 1.8.0_140.

I cannot find the root cause...

[George Stoyanov _Nemetschek Bulgaria_]

Hi

I have the same problem from few days

Thanks