Spring Boot 2.7.5 Released: Key Fixes and Maven Mirror Workarounds
Spring Boot 2.7.5 has been released with over 30 bug fixes and dependency upgrades, includes details on configuration comment detection, Kafka auto‑configuration changes, PEM certificate handling, and provides guidance on switching from the unavailable Alibaba Cloud Maven mirror to Tencent Cloud’s mirror.
Spring Boot 2.7.5 has been released, bringing more than 30 bug fixes and dependency upgrades.
Maven dependency coordinates are available in Maven Central, but cannot be retrieved from the Alibaba Cloud Maven repository.
<code><parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.7.5</version>
<relativePath/> <!-- lookup parent from repository -->
</parent>
</code>Specific updates include:
2. Defect Fixes
Multiple configuration blocks now recognize
!---as comments automatically.
Executor configprops endpoint now correctly displays DataSize properties.
Refactored bean injection in
@KafkaAutoConfigurationfor easier overriding.
PEM‑format certificates in the configuration container are now correctly recognized.
Assertions on
CapturedOutputin Kotlin are significantly faster.
CouchbaseReactiveHealthIndicatornow performs endpoint checks in a non‑blocking manner.
Empty
@DefaultValuecannot be used for collections, maps, or arrays.
3. Suspension of Alibaba Cloud Maven Proxy
To improve the mirror site experience, the Alibaba Cloud Maven repository will undergo a system upgrade in October, during which the mirror will be paused.
If you use the Alibaba Cloud Maven proxy, you will encounter missing dependency errors.
4. Using Tencent Cloud Maven Proxy
Configure Tencent Cloud Maven proxy in
maven/settings.xml:
<code><mirror>
<id>nexus-tencentyun</id>
<mirrorOf>*</mirrorOf>
<name>Nexus tencentyun</name>
<url>http://mirrors.cloud.tencent.com/nexus/repository/maven-public/</url>
</mirror>
</code>Using Tencent Cloud’s multi‑threaded download may trigger a 502 error; simply retry.
Java Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.