Maven dependency mapping fails with "No versions found" in Application Advisor

Products

• VMware Tanzu Spring Essentials

Issue/Introduction

When attempting to generate a new application map using the VMware Tanzu Spring Application Advisor CLI (advisor mapping create), the process fails to discover version availability for specific project coordinates. Even though the system environment is configured with proper Maven paths and the dependencies can be successfully resolved locally via a standard Maven command-line interface, the tool reports that it cannot fetch version listings. This behavior typically occurs in highly secure enterprise environments utilizing internal private artifact repositories.

Environment

 

• Product: VMware Tanzu Spring Essentials

• Component: VMware Tanzu Spring (Application Advisor CLI)

• Version: 25.0.1+11

• Build System: Maven Artifact Repository ecosystem

 

Cause

The Application Advisor CLI relies on parsing the maven-metadata.xml repository file hosted alongside the artifacts to identify, inspect, and evaluate valid upgrade paths. If a dependency or internal library is published to an enterprise repository (such as JFrog Artifactory or Sonatype Nexus) without generating or maintaining this metadata file, the Application Advisor engine cannot determine available versions and halts the mapping process.

Resolution

As this is not directly an issue with Application Advisor, the resolution must be applied on the hosting artifact repository manager, as the Application Advisor CLI is working as designed.

 

• Request the user verify that a valid maven-metadata.xml file is successfully generated and visible in the artifact directory storage hierarchy. If file does not exist, user is requested to follow the steps to create it based on their chosen artifact repository manager (e.g., Artifactory, Nexus).

• Re-run the mapping command from the Application Advisor CLI once the resolution has been applied by the customer.