Test-scoped dependencies are not updated when using custom mappings in App Advisor

Products

• VMware Tanzu Platform Spring

Issue/Introduction

When running Spring App Advisor with a custom mapping file (e.g., using SPRING_ADVISOR_MAPPING_CUSTOM_0_FILEPATH), primary dependencies are updated successfully, but the corresponding -test dependencies (like mybatis-spring-boot-starter-test) remain on their previous versions.

Checking the generated JSON mapping file shows that the test dependency coordinates are present and correctly formatted.

Environment

 

• Spring App Advisor 1.5.x and earlier.

 

Cause

This is a known bug related to how Spring App Advisor translates custom mappings into recipes at runtime. Currently, the recipe generator excludes test-scoped dependencies during its execution, which prevents them from being updated even when they are properly defined in the custom mapping JSON.

Resolution

There is no configuration change required on your end, as the advisor mapping build command is working as intended.

Until a patch is released for Spring App Advisor, you will need to manually bump the version of the affected -test dependencies in your pom.xml or build.gradle file after the Advisor completes its run.