This is an automated email from the ASF dual-hosted git repository. ppkarwasz pushed a commit to branch chore/remove-duplicate-exec-maven-plugin-version in repository https://gitbox.apache.org/repos/asf/logging-parent.git
commit d5e9b12099822c1e5b512c1c90f362c4eec30a3a Author: Piotr P. Karwasz <[email protected]> AuthorDate: Wed Jul 22 14:54:36 2026 +0200 Fix duplicate `exec-maven-plugin.version` from a bad merge Commit 873899ead0b997140568a1d5e1d227d2efa7135b ("Add options to enable Develocity") accidentally re-added an `exec-maven-plugin.version` declaration next to the existing one, most likely due to a badly resolved merge or rebase. Since then Dependabot has been bumping both declarations independently. Maven uses the last declaration, so dropping the first one does not change the effective version (`3.6.3`). This was the only duplicate property in the POM. Assisted-By: Claude Fable 5 <[email protected]> --- pom.xml | 1 - 1 file changed, 1 deletion(-) diff --git a/pom.xml b/pom.xml index 760d15d..bfd5798 100644 --- a/pom.xml +++ b/pom.xml @@ -219,7 +219,6 @@ <bnd-baseline-maven-plugin.version>7.2.3</bnd-baseline-maven-plugin.version> <build-helper-maven-plugin.version>3.6.1</build-helper-maven-plugin.version> <cyclonedx-maven-plugin.version>2.9.1</cyclonedx-maven-plugin.version> - <exec-maven-plugin.version>3.4.1</exec-maven-plugin.version> <exec-maven-plugin.version>3.6.3</exec-maven-plugin.version> <flatten-maven-plugin.version>1.7.3</flatten-maven-plugin.version> <frontend-maven-plugin.version>2.0.0</frontend-maven-plugin.version>
