Sorry if this comes through twice, I wasn't subscribed when I sent it the first time.
-1 (non-binding) Have not been able to verify the correction for MENFORCER-394 is working. Added example of the issue being reproduced in the staged release. https://issues.apache.org/jira/browse/MENFORCER-394?focusedCommentId=17551314&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17551314 On 2022/06/07 15:30:44 Slawomir Jaranowski wrote: > Hi, > > We solved 13 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12341008 > > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MENFORCER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1761/ > https://repository.apache.org/content/repositories/maven-1761/org/apache/maven/enforcer/enforcer/3.1.0/enforcer-3.1.0-source-release.zip > > Source release checksum(s): > enforcer-3.1.0-source-release.zip - SHA-512 : > 7f39b05774cbf0fe51b8660beb9abf723c7c0f0ae87cc472f5045e95f0c535cb7810703007059dda6676ea08eca379dd628a6394651224110bf3dd95a4966580 > > Staging site: > https://maven.apache.org/enforcer-archives/enforcer-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -- > Sławomir Jaranowski >
