How do I resolve incorrectly populated GAV information from jar files?

As of Artifactory v3.5.1 (March, 2015), when a ‘.jar’ file is deployed via the Artifactory UI, our code looks in the “META-INF/maven/”-directory, and uses the first ‘pom.xml’-file that it finds in that directory.


Usually, this will be the pom-file of the .jar that is being deployed, and will provide the correct maven GAV information. However, we have encountered some .jars where pom-files from dependencies are found instead, resulting in the deployment dialogue populating with incorrect GAV information, pulled from the first pom that is found.

If this occurs, you may need to alter either the “Target Path” field, or the individual fields under “Deploy as Maven Artifact” to reflect the correct maven GAV information.  


If you check the “Also Deploy Jar’s Internal POM/Generate Default POM”-checkbox, the information that is populated will be incorrect and will need to be replaced with that of the correct pom.xml.