Limiting repository releases in Spring App Advisor mapping commands

Products

• VMware Tanzu Platform Spring

Issue/Introduction

When using the advisor mapping build command (e.g., advisor mapping build -r https://github.com/...), the tool may process all available library versions or releases from the repository. This can be inefficient and time-consuming, especially when only specific releases (such as those supporting Spring Boot 4) are required for the mapping.

Cause

The advisor mapping build command is part of a legacy mapping method available in Spring App Advisor versions 1.5.5 and earlier. This command, along with cf repo build-mapping, requires explicit Maven repository configuration and lacks the efficiency or native filtering options needed to limit the scope of releases during the mapping process.

Resolution

To address these efficiency concerns and better manage repository releases, the advisor mapping build command has been deprecated in favor of a newer, more optimized command introduced in version 1.5.6.

To resolve this issue, follow these steps:

1. Upgrade Spring App Advisor: Ensure you are using Spring App Advisor version 1.5.6 or higher.
2. Use the New Command: Replace the legacy advisor mapping build command with the new advisor mapping create command.
3. Verify Results: The advisor mapping create command is significantly faster and more reliable, allowing for a more streamlined mapping process that avoids the overhead of processing unnecessary historical library versions.

Additional Information

This information can also be found in Spring App Advisor latest doc.