Spring Boot Application Builds Fail Due To Missing Release Bundles

Products

• VMware Tanzu Spring Runtime

Issue/Introduction

When developing applications, customers may want to access Spring Enterprise releases directly from Spring Enterprise Subscription artifact repositories. More info here.

If dependencies are not available in the Spring Commercial repository, Spring Boot application builds will fail with the below error. This only applies if maven is pulling dependencies from Spring Enterprise Repo (https://packages.broadcom.com/artifactory/spring-enterprise/)

Error: ] Some problems were encountered while processing the POMs:
---
Error:  Non-resolvable import POM: The following artifacts could not be resolved: org.springframework.integration:spring-integration-bom:pom:6.2.13 (absent): Could not find artifact org.springframework.integration:spring-integration-bom:pom:6.2.13 in central #### @ org.springframework.boot:spring-boot-dependencies:3.2.15, /home/runner/.m2/repository/org/springframework/boot/spring-boot-dependencies/3.2.15/spring-boot-dependencies-3.2.15.pom, line 2886, column 19
---
Error:  The build could not read 1 project -> [Help 1]
---
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
---
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Error:  [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Error: Process completed with exit code 1.

The two releases missing in this example are below:

integration:spring-integration-bom:pom:6.2.13

pulsar:spring-pulsar-bom:pom:1.0.14

Cause

The release bundle step is missing in the GitHub workflow or there was a failure in the upload step.

Resolution

Open a support ticket and the support team will work with the product team to get the release bundles uploaded.