incorrect artifactId in x-pack-core Maven pom

[jecstarinnovations]

Elasticsearch version (bin/elasticsearch --version): ersion: 6.5.4, Build: oss/tar/d2ef93d/2018-12-17T21:17:40.758843Z, JVM: 1.8.0_191

Plugins installed: Default plugins

JVM version (java -version): OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)

OS version (uname -a if on a Unix-like system): Linux jecstar-laptop 4.19.13-300.fc29.x86_64 #1 SMP Sat Dec 29 22:54:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Description of the problem including expected versus actual behavior: I am unable to compile a gradle project when the java x-pack transport client is used as a compile dependency. The build fails with the following exception:

  > Could not resolve org.elasticsearch.plugin:x-pack-core:6.5.4.
     > inconsistent module metadata found. Descriptor: org.elasticsearch.plugin:core:6.5.4 Errors: bad module name: expected='x-pack-core' found='core'

The pom file located at https://artifacts.elastic.co/maven/org/elasticsearch/plugin/x-pack-core/6.5.4/x-pack-core-6.5.4.pom does indeed contain <artifactId>core</artifactId> instead of <artifactId>x-pack-core</artifactId>

Steps to reproduce:
Exctract the attached project and build it with ./gradlew build
xpack-build-error.tar.gz

[elasticmachine]

Pinging @elastic/es-core-infra

[alpar-t]

This broke with #32351

[Tiuser4567]

Hi @atorok
Just like to ask if the pom files of all affected versions (e.g. 6.5.2, ... 6.5.4 and so) will be updated in the elasticsearch maven repo https://artifacts.elastic.co/maven?
Or is there another updated repo I can refer to?

Thank you

[alpar-t]

We don't update already published artifacts. The fix will be coming in the versions labeled on the PR only.