From 79a043063124698da41a8696b69ed312454f769e Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Tue, 18 Jan 2022 08:57:07 +0100 Subject: [PATCH] Polishing. Use JPA version number for Envers to properly upgrade the BOM for Spring Data 3. It doesn't hurt to do the same for 2.x as version numbers of JPA and Envers are the same after the 2.0 version bump. Closes #200 --- .../java/org/springframework/data/release/model/Projects.java | 1 - 1 file changed, 1 deletion(-) diff --git a/src/main/java/org/springframework/data/release/model/Projects.java b/src/main/java/org/springframework/data/release/model/Projects.java index a82cd93..ecb2eb7 100644 --- a/src/main/java/org/springframework/data/release/model/Projects.java +++ b/src/main/java/org/springframework/data/release/model/Projects.java @@ -56,7 +56,6 @@ public class Projects { JPA = new Project("DATAJPA", "JPA", Tracker.GITHUB) // .withDependencies(COMMONS) // - // TODO: This is only for Spring Data 3.0. .withAdditionalArtifacts(ArtifactCoordinates.SPRING_DATA.artifacts("spring-data-envers")); MONGO_DB = new Project("DATAMONGO", "MongoDB", Tracker.GITHUB) //