[java-mvn-enforcer] branch main updated: Do not check m2 when building parent project
Codeberg
noreply at shibboleth.net
Thu Oct 22 09:50:54 UTC 2026
This is an automated email from the git hooks/post-receive script.
codeberg pushed a commit to branch main
in repository java-mvn-enforcer.
View the commit online:
https://codeberg.org/Shibboleth/java-mvn-enforcer/commit/e22890e6341ebf06093d9339cf0cf7e8ad4a41ae
The following commit(s) were added to refs/heads/main by this push:
new e22890e Do not check m2 when building parent project
e22890e is described below
commit e22890e6341ebf06093d9339cf0cf7e8ad4a41ae
Author: Rod Widdowson <rdw at steadingsoftware.com>
AuthorDate: Thu Oct 22 10:49:50 2026 +0100
Do not check m2 when building parent project
The latest enforcer release has issues with the fact that it
is a parentless project.
The M2check is meaningless for non jar project
---
parent/.check-m2 | 1 -
1 file changed, 1 deletion(-)
diff --git a/parent/.check-m2 b/parent/.check-m2
deleted file mode 100644
index 048849a..0000000
--- a/parent/.check-m2
+++ /dev/null
@@ -1 +0,0 @@
-This file provokes a signature check of the maven repository unless overridden by the no-check-m2 property.
\ No newline at end of file
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
More information about the commits
mailing list