Captured 2026-09-18 from repo1.maven.org (Maven Central):
https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-starter-aspectj/4.1.1/spring-boot-starter-aspectj-4.1.1.pom

<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-aspectj</artifactId>
<version>4.1.1</version>
<name>spring-boot-starter-aspectj</name>
<description>Starter for using aspect-oriented programming with AspectJ</description>

<dependencies>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter</artifactId>
    <version>4.1.1</version>
    <scope>compile</scope>
  </dependency>
  <dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-aop</artifactId>
    <version>7.0.9</version>
    <scope>compile</scope>
  </dependency>
  <dependency>
    <groupId>org.aspectj</groupId>
    <artifactId>aspectjweaver</artifactId>
    <version>1.9.25.1</version>
    <scope>compile</scope>
  </dependency>
</dependencies>

The renamed starter's own POM declares exactly spring-aop + aspectjweaver as compile
dependencies -- the same two jars this module's own pom.xml already lists as the reason it
depends on spring-boot-starter-aspectj. There is no missing third piece and no behavioural
difference from assembling the two jars by hand; the starter just does it for you, correctly
versioned, in one line.