[java-shib-metadata] branch main updated: JPAR-190 Investigate an enforcer to check all jars and poms ~/.m2/.... towards the end of a build

[Rod Widdowson]

This is an automated email from the git hooks/post-receive script.

rdw pushed a commit to branch main
in repository java-shib-metadata.

View the commit online:
http://git.shibboleth.net/view/?p=java-shib-metadata.git;a=commit;h=1d35336d4491b136c740d07682bc696c8893555c

The following commit(s) were added to refs/heads/main by this push:
     new 1d35336d JPAR-190 Investigate an enforcer to check all jars and poms ~/.m2/.... towards the end of a build
1d35336d is described below

commit 1d35336d4491b136c740d07682bc696c8893555c
Author: Rod Widdowson <rdw at steadingsoftware.com>
AuthorDate: Sun Oct 9 14:34:56 2022 +0100

    JPAR-190 Investigate an enforcer to check all jars and poms ~/.m2/.... towards the end of a build
    
    https://shibboleth.atlassian.net/browse/JPAR-190
    
    shib-metadata-bom does not create a target directory
    
    Instead arrange for the m2 signature report to be written into the shibd-metadata-bom
    directory.
---
 .gitignore                | 1 +
 shib-metadata-bom/pom.xml | 5 +++++
 2 files changed, 6 insertions(+)

diff --git a/.gitignore b/.gitignore
index 7ad60a98..aca5a3b4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,3 +20,4 @@ test-output
 .project
 .classpath
 .settings
+shib-metadata-bom/m2SignatureReport.txt
diff --git a/shib-metadata-bom/pom.xml b/shib-metadata-bom/pom.xml
index a4e5bac4..cd90b8b0 100644
--- a/shib-metadata-bom/pom.xml
+++ b/shib-metadata-bom/pom.xml
@@ -15,6 +15,11 @@
     <artifactId>shib-metadata-bom</artifactId>
     <packaging>pom</packaging>
     
+    <properties>
+      <!-- This project does not create a target, so the M2 check needs to go elsewhere -->
+      <maven-dist-enforcer-data.m2ReportPath>${basedir}\m2SignatureReport.txt</maven-dist-enforcer-data.m2ReportPath>
+    </properties>
+
     <dependencyManagement>
         <dependencies>
             <dependency>

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.