asmhatre/spring-boot-demo
1
0
Fork 0
Code Activity

resilience: prove spring-boot-starter-aop was renamed to spring-boot-starter-aspectj, not removed

Browse Source 
Maven Central's maven-metadata.xml for both artifact IDs, read together, shows aop's last
release is 4.0.0-M2 and aspectj's first release is 4.0.0-M3 -- a rename at a milestone
boundary, not a drop. The renamed starter's own published POM depends on exactly
spring-aop + aspectjweaver, the two jars this pom.xml's dependency comment already claimed
were needed; this commit adds the reproducible build-break proof, the metadata/POM evidence,
and a new doc chapter, and backs the corrected companion-repo links from the resilience4j-
circuit-breaker-spring-boot post.
This commit is contained in:
asmhatre
2026-09-18 08:34:06 +00:00
parent baff043748
commit 604291067e
9 changed files with 179 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resilience/docs/output/00b-starter-aspectj-metadata-timeline.txt
+33
View File
@@ -0,0 +1,33 @@
Captured 2026-09-18 from repo1.maven.org (Maven Central), not an aggregator or blog.
--- org/springframework/boot/spring-boot-starter-aop/maven-metadata.xml ---
<latest>4.0.0-M2</latest>
<release>4.0.0-M2</release>
... version list ends at:
<version>3.5.16</version>
<version>4.0.0-M1</version>
<version>4.0.0-M2</version>
</versions>
<lastUpdated>20260625105758</lastUpdated>
--- org/springframework/boot/spring-boot-starter-aspectj/maven-metadata.xml ---
<latest>4.2.0-M1</latest>
<release>4.2.0-M1</release>
... version list starts at:
<version>4.0.0-M3</version>
<version>4.0.0-RC1</version>
<version>4.0.0-RC2</version>
<version>4.0.0</version>
<version>4.0.1</version>
...
<version>4.1.0</version>
<version>4.1.1</version>
<version>4.2.0-M1</version>
</versions>
<lastUpdated>20260820133928</lastUpdated>
Reading the two lists together: spring-boot-starter-aop's last-ever release is 4.0.0-M2.
spring-boot-starter-aspectj's first-ever release is 4.0.0-M3 -- the very next milestone in the
4.0 line. It then carries through 4.0.0-RC1, RC2, the 4.0.0 GA, every 4.0.x and 4.1.x patch, and
into the 4.2.0-M1 pre-release. That is a rename at a specific milestone boundary, not two
unrelated artifacts and not a starter that was dropped with nothing replacing it.