Re: [RESULT] [VOTE] Apache Maven Surefire 3.0.0-M7
David, Sending from my mobile, so will be short. I wrote the roadmap with purpose you was talking about. We can discuss it in a voice conf which would be much faster and you can help us too but it would not be done by the way to fire a random PRs. I neededed a break because of my job and illness but this happens. Regarding the release of 2.22.3, this is ready to go. Maybe somebody wants to backport some latest fixes... T Dňa pi 10. 6. 2022, 19:52 David Karr napísal(a): > Well, we had found that we couldn't get all the required variations of > JUnit 5 working in Maven without the M release, so we had to upgrade. We > have tested our scenarios with M7, including test suites and mixed Junit4 > and JUnit5 tests, and we're not seeing any problems (including one scenario > that produced the BufferOverflow exception with M6). > > The thing is, if you're not confident enough with it to produce a non-M > release, that makes us a little nervous also. The scenarios we've tested > are a tiny fraction of the services that will be using this. I don't expect > to see any unexpected problems, but that's normal. > > However, I can certainly understand you concluding you don't have enough > data to really be confident it's fully ready. The one thing we've > determined in our testing is that if a particular service finds some > unexpected problem at any level of the JUnit 5 upgrade (starting with > simply upgrading the surefire version to 3.0.0-M7), they can simply stay > with JUnit 4 and Surefire 2.x, and they can move forward with that, while > we file that as a scenario that we need to troubleshoot. We can live with > that. > > On Wed, Jun 8, 2022 at 6:20 PM Olivier Lamy wrote: > > > On Wed, 8 Jun 2022 at 04:29, David Karr > > wrote: > > > > > Now that M7 is released, I have a feeling I know the answer to this, > but > > > what are your thoughts about when a full release will go out with these > > > latest changes? I'm currently evaluating whether we can upgrade our > > > internal platform to support Junit 5. As far as we know, M7 will > address > > > the last problem we were seeing (buffer overflow), and we'll be testing > > > that this morning, but my "platform" team only has a small set of > > services > > > we can easily test platform upgrades with. Our platform is used by a > > large > > > number of services. Using a "beta" version carries some amount of > > > indeterminate risk (sort of redundant), so I have to be more careful > > about > > > planning for contingencies if we discover unexpected problems from the > M7 > > > version in other services we don't directly support. Those > contingencies > > > include staying on Surefire 2.22.0, but still using Spring Boot 2.3.12 > > > (upgrading this will be coming soon), and only using JUnit 4. > > > > > > > > > Well I think using Mx is because we are a bit conservative :) > > version naming is a bit of a chicken and egg problem! > > We'd like to have more feedback/tests (even issues :)) etc.. from the > real > > world but as it's called M* people do not upgrade. > > I do not see real issues with junit5. > > BUT I think there are still some problems with JPMS and the default (and > > non configurable) options used. > > Let me explain that. First you need to know surefire (and few other > plugins > > such compiler, javadoc) rely on a library called plexus-java which from a > > list of jars will parse all the module-info files to build a sort of > graph > > and so build the module-path and the classpath. > > 3.0.0-M5 has been released in June 2020 with plexus-java 1.0.5 from > > February 2020. > > 3.0.0-M6 has been released at the end of March 2022 with plexus-java > 1.1.1 > > from January 2022. > > It's always 2 years between those releases and by the way plenty of > changes > > in the plexus-java library (because of some issues with compiler, javadoc > > etc..) > > (With my committer of Jetty project hat) we use JPMS now and moving from > > 3.0.0-M5 to M6 is impossible because of > > https://issues.apache.org/jira/browse/SUREFIRE-2057 which is breaking > > change in plexus-java > > and now upgrading to M7 is impossible either because of another issue > > (which I need to create a jira for it). (but there is a gist explaining > the > > problem here > > https://gist.github.com/olamy/d651e21fd89b73612a42e3617a1d0261 > > ) > > Ideally I'd like to have more configurable options for jpms (e.g module > > graph resolution) because actually it's based on some assumptions which > can > > be wrong for some use cases. > > I'm currently collecting use cases etc... Then I will create a Jira to > ask > > for comments (such as what do you want guys to be configurable for jpms: > > test scope should be in module-path or classpath, same for provided, do > we > > need to add automatically providers to the module-path even if it's a > test > > dependency). > > I think this needs to be fixed before removing the M* :) because jpms get > > more and more adoptions now. > > > > >
Re: [VOTE] Release Maven Resolver version 1.8.1
+1 Reproducible Build ok: reference done with JDK 8 on Windows Regards, Hervé Le vendredi 10 juin 2022, 17:50:12 CEST Michael Osipov a écrit : > Hi, > > We solved 8 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628 > rsion=12351656 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%2 > 0resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver > > Staging repo: > https://repository.apache.org/content/repositories/maven-1762/ > https://repository.apache.org/content/repositories/maven-1762/org/apache/mav > en/resolver/maven-resolver/1.8.1/maven-resolver-1.8.1-source-release.zip > > Source release checksum(s): > maven-resolver-1.8.1-source-release.zip > 2137c921c5264e1a15a091586a445dbaed83cef4cbf766e76c5670a4199cadf82e4789f8614d > 13bbd150d93ce5c9e017cb059306c683807862ac5dde9dab7e4f > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Apache Maven Enforcer Plugin 3.1.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.1.0 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https://maven.apache.org/enforcer/maven-enforcer-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-enforcer-plugin 3.1.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/enforcer/download.cgi Release Notes - Maven Enforcer Plugin - Version 3.1.0 ** Bug * [MENFORCER-389] - Exclusions are not considered when looking at parent for requireReleaseDeps * [MENFORCER-391] - requireUpperBoundDeps does not fail when packaging is 'war' * [MENFORCER-394] - DependencyConvergence in 3.0.0 fails on provided scoped dependencies * [MENFORCER-395] - NPE on requireReleaseDeps with non-matching includes * [MENFORCER-402] - RequireUpperBoundDeps now follow scope provided transitive dependencies * [MENFORCER-421] - Use currently build artifacts in IT tests ** Improvement * [MENFORCER-404] - Shared GitHub Actions * [MENFORCER-409] - Log at ERROR level when is set * [MENFORCER-420] - Reuse getDependenciesToCheck results across rules ** Dependency upgrade * [MENFORCER-372] - Switch to JUnit5 * [MENFORCER-403] - Upgrade aether-util > maven-core > enforcer * [MENFORCER-418] - Upgrade Parent to 36 * [MENFORCER-419] - Upgrade Maven to 3.2.5 Enjoy, -The Apache Maven team
Re: [RESULT] [VOTE] Apache Maven Surefire 3.0.0-M7
Well, we had found that we couldn't get all the required variations of JUnit 5 working in Maven without the M release, so we had to upgrade. We have tested our scenarios with M7, including test suites and mixed Junit4 and JUnit5 tests, and we're not seeing any problems (including one scenario that produced the BufferOverflow exception with M6). The thing is, if you're not confident enough with it to produce a non-M release, that makes us a little nervous also. The scenarios we've tested are a tiny fraction of the services that will be using this. I don't expect to see any unexpected problems, but that's normal. However, I can certainly understand you concluding you don't have enough data to really be confident it's fully ready. The one thing we've determined in our testing is that if a particular service finds some unexpected problem at any level of the JUnit 5 upgrade (starting with simply upgrading the surefire version to 3.0.0-M7), they can simply stay with JUnit 4 and Surefire 2.x, and they can move forward with that, while we file that as a scenario that we need to troubleshoot. We can live with that. On Wed, Jun 8, 2022 at 6:20 PM Olivier Lamy wrote: > On Wed, 8 Jun 2022 at 04:29, David Karr > wrote: > > > Now that M7 is released, I have a feeling I know the answer to this, but > > what are your thoughts about when a full release will go out with these > > latest changes? I'm currently evaluating whether we can upgrade our > > internal platform to support Junit 5. As far as we know, M7 will address > > the last problem we were seeing (buffer overflow), and we'll be testing > > that this morning, but my "platform" team only has a small set of > services > > we can easily test platform upgrades with. Our platform is used by a > large > > number of services. Using a "beta" version carries some amount of > > indeterminate risk (sort of redundant), so I have to be more careful > about > > planning for contingencies if we discover unexpected problems from the M7 > > version in other services we don't directly support. Those contingencies > > include staying on Surefire 2.22.0, but still using Spring Boot 2.3.12 > > (upgrading this will be coming soon), and only using JUnit 4. > > > > > Well I think using Mx is because we are a bit conservative :) > version naming is a bit of a chicken and egg problem! > We'd like to have more feedback/tests (even issues :)) etc.. from the real > world but as it's called M* people do not upgrade. > I do not see real issues with junit5. > BUT I think there are still some problems with JPMS and the default (and > non configurable) options used. > Let me explain that. First you need to know surefire (and few other plugins > such compiler, javadoc) rely on a library called plexus-java which from a > list of jars will parse all the module-info files to build a sort of graph > and so build the module-path and the classpath. > 3.0.0-M5 has been released in June 2020 with plexus-java 1.0.5 from > February 2020. > 3.0.0-M6 has been released at the end of March 2022 with plexus-java 1.1.1 > from January 2022. > It's always 2 years between those releases and by the way plenty of changes > in the plexus-java library (because of some issues with compiler, javadoc > etc..) > (With my committer of Jetty project hat) we use JPMS now and moving from > 3.0.0-M5 to M6 is impossible because of > https://issues.apache.org/jira/browse/SUREFIRE-2057 which is breaking > change in plexus-java > and now upgrading to M7 is impossible either because of another issue > (which I need to create a jira for it). (but there is a gist explaining the > problem here > https://gist.github.com/olamy/d651e21fd89b73612a42e3617a1d0261 > ) > Ideally I'd like to have more configurable options for jpms (e.g module > graph resolution) because actually it's based on some assumptions which can > be wrong for some use cases. > I'm currently collecting use cases etc... Then I will create a Jira to ask > for comments (such as what do you want guys to be configurable for jpms: > test scope should be in module-path or classpath, same for provided, do we > need to add automatically providers to the module-path even if it's a test > dependency). > I think this needs to be fixed before removing the M* :) because jpms get > more and more adoptions now. > > > > > > > > > > > > > > > On Mon, Jun 6, 2022 at 4:16 PM Olivier Lamy wrote: > > > > > Hi > > > The vote has passed. > > > +1 Enrico, Hervé, Michael, Romain, Slawomor, Olivier > > > > > > PMC quorum reached. I will continue the release process. > > > > > > cheers > > > Olivier > > > > > >
[RESULT] [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
Hi, The vote has passed with the following result: +1 : Slawomir Jaranowski, Sylwester Lachiewicz, Tamás Cservenák, Karl Heinz Marbaise, Olivier Lamy, Herve Boutemy, Michael Osipov -1: Matt Nelson PMC quorum: reached I will promote the source release zip file to Apache distribution area and the artifacts to the central repo. -- Sławomir Jaranowski
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
Hi Matt Thanks for your investigation and example. Your case is something else that is described in issue MENFORCER-394, I added comment in the issue. pt., 10 cze 2022 o 17:23 Matt Nelson napisał(a): > 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=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=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 > > > -- Sławomir Jaranowski
Re: [VOTE] Release Maven Resolver version 1.8.1
+1 woohoo! T On Fri, Jun 10, 2022, 17:50 Michael Osipov wrote: > Hi, > > We solved 8 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351656 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver > > Staging repo: > https://repository.apache.org/content/repositories/maven-1762/ > > https://repository.apache.org/content/repositories/maven-1762/org/apache/maven/resolver/maven-resolver/1.8.1/maven-resolver-1.8.1-source-release.zip > > Source release checksum(s): > maven-resolver-1.8.1-source-release.zip > > 2137c921c5264e1a15a091586a445dbaed83cef4cbf766e76c5670a4199cadf82e4789f8614d13bbd150d93ce5c9e017cb059306c683807862ac5dde9dab7e4f > > Staging site: > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > Guide to testing staged releases: > https://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
[VOTE] Release Maven Resolver version 1.8.1
Hi, We solved 8 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12351656 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20Resolver Staging repo: https://repository.apache.org/content/repositories/maven-1762/ https://repository.apache.org/content/repositories/maven-1762/org/apache/maven/resolver/maven-resolver/1.8.1/maven-resolver-1.8.1-source-release.zip Source release checksum(s): maven-resolver-1.8.1-source-release.zip 2137c921c5264e1a15a091586a445dbaed83cef4cbf766e76c5670a4199cadf82e4789f8614d13bbd150d93ce5c9e017cb059306c683807862ac5dde9dab7e4f Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
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=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=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 >
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
Am 2022-06-09 um 09:29 schrieb Slawomir Jaranowski: wt., 7 cze 2022 o 20:33 Michael Osipov napisał(a): Am 2022-06-07 um 17:30 schrieb Slawomir Jaranowski: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=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. Now this looks good! Michael - does it mean +1? Yes, +1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [MPH-183] effective-pom + verbose should show path to source
IIUC, the idea is to extend path to source from currently model parent- inheritance only to model parent-inheritance and BOM POM, aka dependencyManagement import? really nice improvement I imagine it will happen only on version XML elements, isn't it? I think the "from" should be "imported from" and perhaps for previous tracking, we should explicit "inherited from" another improvement could also be to track interpolation, to know when a version comes from a property. Let's dream of "interpolated by property xxx from gav line ..." this would give quite comprehensive explanation but step by step: dependencyManagement import is really a nice improvement, go, go, go Regards, Hervé Le mardi 7 juin 2022, 17:46:41 CEST Maarten Mulders a écrit : > Hi all, > > Over the past months, I have been working on an enhancement [1] for the > Maven Help Plugin. The enhancement is about the effective-pom goal. If > you pass it the 'verbose' parameter, it will include inline comments > saying "this line of the effective pom is caused by this line in a > different pom": > > >org.example >mng-7344-dep-x >2 > > > This is not so useful when you have a long path of POMs referring to > each other. It will only show the last POM of that trail, but not the > intermediate POMs. This makes it hard for users to understand how their > effective POM was constructed. In the enhanced version, > help:effective-pom -Dverbose would show something like this: > > >org.example >mng-7344-dep-x >2 > > > > (I'm sorry, the output is hard to read in a plain-text email; a > formatted version is available in the JIRA ticket [1].) > > > This enhancement requires changes in three projects: > 1. Maven Help Plugin > 2. Maven Core > 3. Modello > > > > Now that the proof of concept is there, I'd like to ask: is this an > enhancement we want to incorporate into Maven? If so, I'll start by > polishing the code a bit, and then open three separate merge requests. > We can discuss the implementation there. > > One particularly important thing to mention is that I did _not yet_ pay > attention to backward compatibility of the Maven Help Plugin. I believe > we can do this in a decent way - it wasn't the first priority for the > proof of concept. > > > I'm looking forward to hearing your thoughts on this. > > > Thanks, > > > Maarten > > > > [1] https://issues.apache.org/jira/browse/MPH-183 > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
+1 Reproducible Builds ok: reference done with JDK 8 on *nix Regards, Hervé 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=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 > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
+1 On Thu, 9 Jun 2022 at 17:30, Slawomir Jaranowski wrote: > wt., 7 cze 2022 o 20:33 Michael Osipov napisał(a): > > > Am 2022-06-07 um 17:30 schrieb Slawomir Jaranowski: > > > Hi, > > > > > > We solved 13 issues: > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=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. > > > > Now this looks good! > > > > Michael - does it mean +1? > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > -- > Sławomir Jaranowski >
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 07.06.22 17:30, Slawomir Jaranowski wrote: Hi, We solved 13 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.1.0
+1 On Tue, Jun 7, 2022 at 5:31 PM Slawomir Jaranowski wrote: > Hi, > > We solved 13 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520=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 >
