[JIRA] (JMVN-13) Pom Parser cannot read the mvn-endofrcer-data pom

[Rod Widdowson (Jira)]

Rod Widdowson ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=59fb32bbc24efb3c4ed3c977 ) *commented* on JMVN-13 ( https://shibboleth.atlassian.net/browse/JMVN-13?atlOrigin=eyJpIjoiNWNjM2IzZGU2ZTFiNGRkM2E2MTNjZWJlYTI0OTVjNjIiLCJwIjoiaiJ9 )

Re: Pom Parser cannot read the mvn-endofrcer-data pom ( https://shibboleth.atlassian.net/browse/JMVN-13?atlOrigin=eyJpIjoiNWNjM2IzZGU2ZTFiNGRkM2E2MTNjZWJlYTI0OTVjNjIiLCJwIjoiaiJ9 )

Ah, hoisted by ones own petard. The whole thing about the enforcer data is that it isnt a dependency. So it doesn’t get onto the classpath so people cannot smuggle fake keyrings in.

But because it isn’t a dependency when we resolve the jar file we only resolve the jar file. Not the pom file. So when the M2 discovers the jar file it looks for the pom file of the same name in the same directory. But it aint there - because we didn’t need it.
I think that the solution is to add this to the pom file of the dist project

           <plugin>
               <groupId>org.apache.maven.plugins</groupId>
               <artifactId>maven-dependency-plugin</artifactId>
               <executions>
                   <execution>
                       <id>get</id>
                       <phase>verify</phase>
                       <goals>
                           <goal>get</goal>
                       </goals>
                       <configuration>
                           <groupId>net.shibboleth.maven.enforcer.rules</groupId>
                           <artifactId>maven-dist-enforcer-data</artifactId>
                           <version>1.0.0-SNAPSHOT</version>
                       </configuration>
                   </execution>
               </executions>
           </plugin>

It might be nicer to do this on the command line ( mvn dependency:get -DartifactId=maven-dist-enforcer-data -DgroupId=net.shibboleth.maven.enforcer.rules -Dversion=1.0.0-SNAPSHOT ) but that would separate the coordinates of the data into twi places (plus it doesn’t work).

I’ll poke at this over the Holidays when Jenkins is quiet.

( https://shibboleth.atlassian.net/browse/JMVN-13#add-comment?atlOrigin=eyJpIjoiNWNjM2IzZGU2ZTFiNGRkM2E2MTNjZWJlYTI0OTVjNjIiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JMVN-13#add-comment?atlOrigin=eyJpIjoiNWNjM2IzZGU2ZTFiNGRkM2E2MTNjZWJlYTI0OTVjNjIiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100186- sha1:84fa40f )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20211215/369b112c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-ff3cbb9a-dbf6-4f77-98e3-7eebe2c60dd8
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211215/369b112c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-c2b4e21c-7b3d-4cd1-ae75-8765fa46e8ff
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211215/369b112c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-67ebc7c1-000e-4aa0-94b8-d5f0040dc23f
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20211215/369b112c/attachment-0005.png>