[JIRA] (JMVN-24) Enforcer plugin prevents maven-deploy plugin from uploading artifacts

[Rod Widdowson (Jira)]

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

Re: Enforcer plugin prevents maven-deploy plugin from uploading artifacts ( https://shibboleth.atlassian.net/browse/JMVN-24?atlOrigin=eyJpIjoiNzY2YWE4ZDk1ZmQ2NDhmZThiMjFlNDMyMTRlMjNhZmQiLCJwIjoiaiJ9 )

The issue is that with the enforcer fragment in place the deploy mojo used for the idp-distribution phase is entirely different from the mojo used for the other phases (not just a different object, a different loading of that class)

Deploy at end is implemented as “when the number of times I have been called == the number of projects” and the “number of times I have been called “is held in a static

private static final AtomicInteger READYPROJECTSCOUNTER = new AtomicInteger();

The entirely different mojo consumes one of the “number of times I have been called” count into a different static & so badness happens.

I am more than slightly boggled by the though that you can have two entirely different implementations of the same class can be active at once - Classpaths I assume (and there is some playing with classpaths in the enforcer).

Investigations continue,

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

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#100192- sha1:2947bec )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220225/0292442f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-e861d90a-7d9c-4b02-94f4-94f494aa6da2
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220225/0292442f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-640e8529-e35a-4bf4-9cae-e59fbe59ff7c
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220225/0292442f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-b041b49a-399f-4033-923e-2139a3c9bb4a
Type: image/png
Size: 468 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220225/0292442f/attachment-0005.png>