Add jakarta-ee-11 module: Jakarta EE 10 vs 11 API comparison against Spring Boot 4.1.1

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Gth99spB1CzQmBFofXmU4Z
This commit is contained in:
Claude
2026-09-28 08:40:07 +00:00
parent acd63e658b
commit e4f927d7af
14 changed files with 342 additions and 0 deletions
+29
View File
@@ -0,0 +1,29 @@
# jakarta-ee-11
Companion module for the ankurm.com post *Jakarta EE 11 for Spring Developers: What Actually Matters*.
Reads the Jakarta EE 10 and 11 API jars from Maven Central with `javap`, reads Spring Boot 4.1.1's own BOM and configuration metadata, and runs one tiny Boot application to ask the embedded Tomcat which Servlet level it implements. No claim in the post comes from prose.
| Component | Version |
|---|---|
| Spring Boot | 4.1.1 |
| JDK | 25 |
| Maven | 3.9 |
## Run
```bash
./scripts/run-all.sh # regenerates everything under output/
```
## Output
| File | Shows |
|---|---|
| `output/01-boot-managed-jakarta-apis.txt` | Jakarta versions Spring Boot 4.1.1 manages, and four artifacts it does not |
| `output/02-api-diff.txt` | Class and member counts, EE 10 vs EE 11, for Servlet, Persistence, Validation, Annotations, Concurrency |
| `output/03-entitymanager-3.2.txt` | New `EntityManager` methods in Persistence 3.2 |
| `output/04-data-and-concurrency.txt` | Jakarta Data 1.0.2 repository types; `@ManagedExecutorDefinition` in 3.0.0 vs 3.1.1 |
| `output/05-servlet-level.txt` | The running application's Servlet level (written by `ServletLevelTest`) |
| `output/06-spring-data-and-jakarta-data.txt` | Spring Data 4.1.1 jars contain no `jakarta.data` types |
| `output/07-virtual-threads-property.txt` | Boot's `spring.threads.virtual.enabled` property, from shipped metadata |