Re: [VOTE] Release Apache Maven Clean Plugin version 3.5.0
+1 Reproducible Build checked ok: reference build done with JDK 21 on *nix Regards, Hervé Le mercredi 28 mai 2025, 00:20:52 CEST Slawomir Jaranowski a écrit : > Hi, > > We solved 6 issues: > https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 > > There are still a couple of issues left: > https://github.com/apache/maven-clean-plugin/issues > > Changes since the last release: > https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4. > 1...maven-clean-plugin-3.5.0 > > Staging repo: > https://repository.apache.org/content/repositories/maven-2292/ > https://repository.apache.org/content/repositories/maven-2292/org/apache/mav > en/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release. > zip > > Source release checksum(s): > maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : > ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3 > 788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 > > Staging site: > https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ > > NOTE - site build with local patch: > https://github.com/apache/maven-clean-plugin/pull/255 > > 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: Maven 4.0.0 Release - Thoughts?
yep, you can try with jprofiler/jetbrains-profiler/something else and see what be the bottleneck. if the project is...open source, we can have a try too... Xeno Amess 于2025年5月28日周三 17:09写道： > @Sergey Chernov > could you please give a link about the test suites you be using > > Sergey Chernov 于2025年5月27日周二 04:56写道： > >> Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower (!) >> on >> a project of ~900 modules (700 of them are jar). >> Maven 3 builds it in 2m57s, while Maven 4 in 11m48s (reproducible, with >> all >> m2 caches). No build cache solutions enabled to compare pure build time. >> Project is nothing special, just java 17 + kotlin 2.1 compilation (no test >> execution). >> It fits into the same heap memory. The CPU cores load is about the same >> (but 4x longer). >> It seems that somewhere there is a huge overhead. >> >> Were there other performance tests at scale? >> >> >> On Mon, May 26, 2025 at 4:48 PM Maarten Mulders >> wrote: >> >> > Totally agree! I'm not trying to advocate "no more RC's", I'm trying to >> > advocate "last RC should be as close as possible to the final product". >> > And given what has happened between the last RC and today, I don't think >> > we can cut 4.0.0 *today*. The diff is quite large IMO. >> > >> > Thanks, >> > >> > >> > Maarten >> > >> > On May 26th, 2025 at 16:39, Elliotte Rusty Harold wrote: >> > > On Mon, May 26, 2025 at 2:25 PM Maarten Mulders < >> mthmuld...@apache.org> >> > wrote: >> > >> >> > >> That definition makes a lot of sense to me. If we would adhere to >> it, we >> > >> should discipline ourselves after "a" next RC and *not* accept any >> code >> > >> changes *except* for fixing critical uses. >> > > >> > > Be careful not to let the tail wag the dog. if changes are needed, >> > > they're needed. You just need another RC. I would actually prefer that >> > > RCs be identical to the release aside from version number, or even >> > > better that the release candidate binary could simply become the >> > > release, but that's not really how the Maven release process works. >> > > However, critical bug fixes should generate a new RC. Overall I would >> > > prefer much more rigorous versioning. Right now we're pushing RCs with >> > > known unstable APIs, which I would normally consider appropriate for >> > > pre-alpha builds. >> > > >> > >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> > For additional commands, e-mail: dev-h...@maven.apache.org >> > >> > >> >
Re: Maven 4.0.0 Release - Thoughts?
@Sergey Chernov could you please give a link about the test suites you be using Sergey Chernov 于2025年5月27日周二 04:56写道： > Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower (!) on > a project of ~900 modules (700 of them are jar). > Maven 3 builds it in 2m57s, while Maven 4 in 11m48s (reproducible, with all > m2 caches). No build cache solutions enabled to compare pure build time. > Project is nothing special, just java 17 + kotlin 2.1 compilation (no test > execution). > It fits into the same heap memory. The CPU cores load is about the same > (but 4x longer). > It seems that somewhere there is a huge overhead. > > Were there other performance tests at scale? > > > On Mon, May 26, 2025 at 4:48 PM Maarten Mulders > wrote: > > > Totally agree! I'm not trying to advocate "no more RC's", I'm trying to > > advocate "last RC should be as close as possible to the final product". > > And given what has happened between the last RC and today, I don't think > > we can cut 4.0.0 *today*. The diff is quite large IMO. > > > > Thanks, > > > > > > Maarten > > > > On May 26th, 2025 at 16:39, Elliotte Rusty Harold wrote: > > > On Mon, May 26, 2025 at 2:25 PM Maarten Mulders > > > wrote: > > >> > > >> That definition makes a lot of sense to me. If we would adhere to it, > we > > >> should discipline ourselves after "a" next RC and *not* accept any > code > > >> changes *except* for fixing critical uses. > > > > > > Be careful not to let the tail wag the dog. if changes are needed, > > > they're needed. You just need another RC. I would actually prefer that > > > RCs be identical to the release aside from version number, or even > > > better that the release candidate binary could simply become the > > > release, but that's not really how the Maven release process works. > > > However, critical bug fixes should generate a new RC. Overall I would > > > prefer much more rigorous versioning. Right now we're pushing RCs with > > > known unstable APIs, which I would normally consider appropriate for > > > pre-alpha builds. > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: Maven 4.0.0 Release - Thoughts?
IMO LinkedHashSet can work, no need to use LinkedHashMap directly... but I still think it better to see the bottle-neck through real-world running. so let's just find some really biggy open source java projects using maven(if can't, maybe we have to craft one?) Martin Desruisseaux 于2025年5月28日周三 03:52写道： > Hello > > Le 2025-05-26 à 22 h 55, Sergey Chernov a écrit : > > > Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower > > (!) on a project of ~900 modules (700 of them are jar). > > > Regarding performance, some months ago I noticed that Maven contains > loops over elements of a list with a call to `List.contains(…)` inside > the loop. Because `List.contains(…)` itself iterates over the elements, > we implicitly have nested loops, which have a performance cost of O(N²) > where N is the number of elements. Replacing some `ArrayList` by > `LinkedHashMap` may change some O(N²) operations into O(N) operations. > The difference between O(N) and O(N²) is unnoticeable when N is small (I > guess that this is the case of Maven's test suite). But when N become > large enough, the difference between O(N) or O(N²) can become the > difference between completing an operation in a few minutes or requiring > the age of the univers. > > I did not verified if Maven 4 has more nested loops than Maven 3. > Neither I verified if the nested loops happen in algorithms where N can > possibly be large. We do not need (neither we should) replace all > `ArrayList` by `LinkedHashMap`. However, I'm not sure if we have > investigated where such replacements should be done. We may not be able > to do this investigation now, but we could keep the door open for future > performance improvements by replacing `List` by `Collection` in the API. > Even if the implementation stay `ArrayList` for now, it would allow us > to replace some of them by `LinkedHashMap` in the future if we identify > that it could bring a performance benefit. > > However, an objection to this proposal was that the order of elements > matter. We had no good solution in Java 17. But if the upgrade to Java > 21, proposed in a separated thread, is accepted, Maven could replace all > methods returning `java.util.List` by methods returning > `java.util.SequencedCollection` in the API. No change in the > implementation would be done at this stage (we keep the current > `ArrayList`), but a future Maven version would have more flexibility for > addressing the O(N²) kind of bottleneck, if any. > > Martin > >
Re: Maven 4.0.0 Release - Thoughts?
the biggest I found yet is https://github.com/apache/logging-log4j2.git Xeno Amess 于2025年5月28日周三 17:17写道： > IMO LinkedHashSet can work, no need to use LinkedHashMap directly... > but I still think it better to see the bottle-neck through real-world > running. so let's just find some really biggy open source java projects > using maven(if can't, maybe we have to craft one?) > > > Martin Desruisseaux 于2025年5月28日周三 > 03:52写道： > >> Hello >> >> Le 2025-05-26 à 22 h 55, Sergey Chernov a écrit : >> >> > Just tried the 4.0.0-rc-3 comparing with 3.9.9, it's 4x times slower >> > (!) on a project of ~900 modules (700 of them are jar). >> > >> Regarding performance, some months ago I noticed that Maven contains >> loops over elements of a list with a call to `List.contains(…)` inside >> the loop. Because `List.contains(…)` itself iterates over the elements, >> we implicitly have nested loops, which have a performance cost of O(N²) >> where N is the number of elements. Replacing some `ArrayList` by >> `LinkedHashMap` may change some O(N²) operations into O(N) operations. >> The difference between O(N) and O(N²) is unnoticeable when N is small (I >> guess that this is the case of Maven's test suite). But when N become >> large enough, the difference between O(N) or O(N²) can become the >> difference between completing an operation in a few minutes or requiring >> the age of the univers. >> >> I did not verified if Maven 4 has more nested loops than Maven 3. >> Neither I verified if the nested loops happen in algorithms where N can >> possibly be large. We do not need (neither we should) replace all >> `ArrayList` by `LinkedHashMap`. However, I'm not sure if we have >> investigated where such replacements should be done. We may not be able >> to do this investigation now, but we could keep the door open for future >> performance improvements by replacing `List` by `Collection` in the API. >> Even if the implementation stay `ArrayList` for now, it would allow us >> to replace some of them by `LinkedHashMap` in the future if we identify >> that it could bring a performance benefit. >> >> However, an objection to this proposal was that the order of elements >> matter. We had no good solution in Java 17. But if the upgrade to Java >> 21, proposed in a separated thread, is accepted, Maven could replace all >> methods returning `java.util.List` by methods returning >> `java.util.SequencedCollection` in the API. No change in the >> implementation would be done at this stage (we keep the current >> `ArrayList`), but a future Maven version would have more flexibility for >> addressing the O(N²) kind of bottleneck, if any. >> >> Martin >> >>
Re: Maven 4.0.0 Release - Thoughts?
After considering the concerns about API stability, plugin compatibility, and the performance issues reported by Sergey (4x slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we should opt for an rc4 to address these issues. My proposal is to release a final release candidate (rc4) soon, aiming for a General Availability (GA) release in September. Post rc4, I suggest creating a 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API changes like records and sequenced collections, as well as new features such as mixins, cascading profiles, server aliases, JDK 21 (still under discussion) and more The recent API changes for JPMS, as Martin noted, only affect the experimental API, so they shouldn’t block the release. On Matthias’s suggestion, enabling GitHub Issues across all repositories before the GA seems like a good idea to improve user feedback. Let’s focus on stabilizing rc4 and addressing performance bottlenecks, possibly exploring Martin’s O(N²) concerns with profiling, as Sergey offered. What do you think about this plan? On a side note, I created a few months ago a project to check Maven 4 compatibility with all Apache projects using Maven. The results for RC-3 can be found at https://github.com/gnodet/maven4-testing/issues/2812. Most of the errors are caused by the use of incompatible plugins (which needs to be updated) or incorrect POMs (as Maven 4 is more strict about a few things). What would be nice is a tool to integrate in the shell that would fix those known incompatibilities, so that users would have an easier migration path. And we could apply it to this project to make more green boxes. Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a écrit : > > Hey Maven Devs, > > We're gearing up to release a new version from the master branch. I'm > thinking we should go for 4.0.0 instead of rc-4. What do you all think? Any > feedback or ideas on the versioning or release plan? Let’s hear it! > > Cheers, > > Guillaume > > -- Guillaume Nodet - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Clean Plugin version 3.5.0
Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.25 00:20, Slawomir Jaranowski wrote: Hi, We solved 6 issues: https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 There are still a couple of issues left: https://github.com/apache/maven-clean-plugin/issues Changes since the last release: https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 Staging repo: https://repository.apache.org/content/repositories/maven-2292/ https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip Source release checksum(s): maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 Staging site: https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ NOTE - site build with local patch: https://github.com/apache/maven-clean-plugin/pull/255 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 Clean Plugin version 3.5.0
+1 śr., 28 maj 2025, 14:30 użytkownik Karl Heinz Marbaise napisał: > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 28.05.25 00:20, Slawomir Jaranowski wrote: > > Hi, > > > > We solved 6 issues: > > https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 > > > > There are still a couple of issues left: > > https://github.com/apache/maven-clean-plugin/issues > > > > Changes since the last release: > > > https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2292/ > > > https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip > > > > Source release checksum(s): > > maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : > > > ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ > > > > NOTE - site build with local patch: > > https://github.com/apache/maven-clean-plugin/pull/255 > > > > 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 Clean Plugin version 3.5.0
I see test failures with Maven 3.9.9. Are these expected to work? Maybe a misconfig somewhere? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT:clean (default-clean) on project exclude-default-dirs: The plugin org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT requires Maven version 4.0.0-rc-3 -> [Help 1] ... [INFO] Build Summary: [INFO] Passed: 0, Failed: 11, Errors: 0, Skipped: 0 [INFO] - [ERROR] The following builds failed: [ERROR] * non-existent-base-dirs/pom.xml [ERROR] * symlink-dont-follow/pom.xml [ERROR] * file-sets-includes-excludes/pom.xml [ERROR] * file-sets-relative-paths/pom.xml [ERROR] * file-sets-absolute-paths/pom.xml [ERROR] * only-test-clean/pom.xml [ERROR] * fast-delete/pom.xml [ERROR] * default/pom.xml [ERROR] * dangling-symlinks/pom.xml [ERROR] * exclude-default-dirs/pom.xml [ERROR] * special-characters/pom.xml [INFO] - [INFO] [INFO] BUILD FAILURE On Wed, May 28, 2025 at 12:30 PM Karl Heinz Marbaise wrote: > > Hi, > > +1 from me. > > Kind regards > Karl Heinz Marbaise > On 28.05.25 00:20, Slawomir Jaranowski wrote: > > Hi, > > > > We solved 6 issues: > > https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 > > > > There are still a couple of issues left: > > https://github.com/apache/maven-clean-plugin/issues > > > > Changes since the last release: > > https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-2292/ > > https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip > > > > Source release checksum(s): > > maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : > > ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ > > > > NOTE - site build with local patch: > > https://github.com/apache/maven-clean-plugin/pull/255 > > > > 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 > -- Elliotte Rusty Harold elh...@ibiblio.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 Clean Plugin version 3.5.0
OK, looks like that was in the 4.0 branch and this is for the 3,x branch. In the 3.x branch there's one unused test dependency that can be removed, nothing serious I can see. On Wed, May 28, 2025 at 12:44 PM Elliotte Rusty Harold wrote: > > I see test failures with Maven 3.9.9. Are these expected to work? > Maybe a misconfig somewhere? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT:clean > (default-clean) on project exclude-default-dirs: The plugin > org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT > requires Maven version 4.0.0-rc-3 -> [Help 1] > ... > [INFO] Build Summary: > [INFO] Passed: 0, Failed: 11, Errors: 0, Skipped: 0 > [INFO] - > [ERROR] The following builds failed: > [ERROR] * non-existent-base-dirs/pom.xml > [ERROR] * symlink-dont-follow/pom.xml > [ERROR] * file-sets-includes-excludes/pom.xml > [ERROR] * file-sets-relative-paths/pom.xml > [ERROR] * file-sets-absolute-paths/pom.xml > [ERROR] * only-test-clean/pom.xml > [ERROR] * fast-delete/pom.xml > [ERROR] * default/pom.xml > [ERROR] * dangling-symlinks/pom.xml > [ERROR] * exclude-default-dirs/pom.xml > [ERROR] * special-characters/pom.xml > [INFO] - > [INFO] > > [INFO] BUILD FAILURE > > > > On Wed, May 28, 2025 at 12:30 PM Karl Heinz Marbaise > wrote: > > > > Hi, > > > > +1 from me. > > > > Kind regards > > Karl Heinz Marbaise > > On 28.05.25 00:20, Slawomir Jaranowski wrote: > > > Hi, > > > > > > We solved 6 issues: > > > https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 > > > > > > There are still a couple of issues left: > > > https://github.com/apache/maven-clean-plugin/issues > > > > > > Changes since the last release: > > > https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-2292/ > > > https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip > > > > > > Source release checksum(s): > > > maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : > > > ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 > > > > > > Staging site: > > > https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ > > > > > > NOTE - site build with local patch: > > > https://github.com/apache/maven-clean-plugin/pull/255 > > > > > > 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 > > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org -- Elliotte Rusty Harold elh...@ibiblio.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 Clean Plugin version 3.5.0
On Wed, 28 May 2025 at 14:46, Elliotte Rusty Harold wrote: > I see test failures with Maven 3.9.9. Are these expected to work? > Maybe a misconfig somewhere? > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT:clean > (default-clean) on project exclude-default-dirs: The plugin > org.apache.maven.plugins:maven-clean-plugin:4.0.0-beta-3-SNAPSHOT > requires Maven version 4.0.0-rc-3 -> [Help 1] > I have released version 3.5.0 from branch: maven-clean-plugin-3.x Mentioned errors are from master branch - version 4.x > ... > [INFO] Build Summary: > [INFO] Passed: 0, Failed: 11, Errors: 0, Skipped: 0 > [INFO] - > [ERROR] The following builds failed: > [ERROR] * non-existent-base-dirs/pom.xml > [ERROR] * symlink-dont-follow/pom.xml > [ERROR] * file-sets-includes-excludes/pom.xml > [ERROR] * file-sets-relative-paths/pom.xml > [ERROR] * file-sets-absolute-paths/pom.xml > [ERROR] * only-test-clean/pom.xml > [ERROR] * fast-delete/pom.xml > [ERROR] * default/pom.xml > [ERROR] * dangling-symlinks/pom.xml > [ERROR] * exclude-default-dirs/pom.xml > [ERROR] * special-characters/pom.xml > [INFO] - > [INFO] > > [INFO] BUILD FAILURE > > > > On Wed, May 28, 2025 at 12:30 PM Karl Heinz Marbaise > wrote: > > > > Hi, > > > > +1 from me. > > > > Kind regards > > Karl Heinz Marbaise > > On 28.05.25 00:20, Slawomir Jaranowski wrote: > > > Hi, > > > > > > We solved 6 issues: > > > https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 > > > > > > There are still a couple of issues left: > > > https://github.com/apache/maven-clean-plugin/issues > > > > > > Changes since the last release: > > > > https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-2292/ > > > > https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip > > > > > > Source release checksum(s): > > > maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : > > > > ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 > > > > > > Staging site: > > > https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ > > > > > > NOTE - site build with local patch: > > > https://github.com/apache/maven-clean-plugin/pull/255 > > > > > > 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 > > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Sławomir Jaranowski
Re: Maven 4.0.0 Release - Thoughts?
jetty is a good example.
mvn3 can build but mvn4 cannot.
maven-assembly-plugin:3.7.1 wrongly invoking a bom sub-project
[INFO] ---< org.eclipse.jetty.ee10:jetty-ee10-bom
>
[INFO] Building EE10 :: BOM 12.0.22-SNAPSHOT
[90/354]
[INFO] from jetty-ee10/jetty-ee10-bom/pom.xml
[INFO] [ pom
]-
[INFO] Going to calculate checksum for project
[groupId=org.eclipse.jetty.ee10, artifactId=jetty-ee10-bom,
version=12.0.22-SNAPSHOT]
[INFO] Project inputs calculated in 0 ms. XXMM checksum [7b7b6120251dfd1d]
calculated in 0 ms.
[INFO] Attempting to restore project org.eclipse.jetty.ee10:jetty-ee10-bom
from build cache
[INFO] Local build found by checksum 7b7b6120251dfd1d
[INFO] Found cached build, restoring org.eclipse.jetty.ee10:jetty-ee10-bom
from cache by checksum 7b7b6120251dfd1d
[WARNING] Cached build doesn't contains all requested plugin executions
(missing:
[org.apache.maven.plugins:maven-resources-plugin:3.3.1:copy-resources
{execution: copy-resources},
org.apache.maven.plugins:maven-assembly-plugin:3.7.1:single {execution:
config-assembly}]), cannot restore
[INFO] Local build was not found by checksum 7b7b6120251dfd1d for
org.eclipse.jetty.ee10:jetty-ee10-bom
[INFO]
[INFO] --- spotless:2.44.4:check (default) @ jetty-ee10-bom ---
[INFO] Index file does not exist. Fallback to an empty index
[INFO] Sorting file /tmp/pom11239457262347372795.xml
[INFO] Pom file is already sorted, exiting
[INFO] Spotless.Pom is keeping 1 files clean - 0 needs changes to be clean,
1 were already clean, 0 were skipped because caching determined they were
already clean
[INFO]
[INFO] --- checkstyle:3.6.0:check (checkstyle-check) @ jetty-ee10-bom ---
[INFO] 开始检查……
检查完成。
[INFO] You have 0 Checkstyle violations.
[INFO]
[INFO] --- enforcer:3.5.0:enforce (ban-javax-servlet-api) @ jetty-ee10-bom
---
[INFO] Rule 0:
org.apache.maven.enforcer.rules.dependency.BannedDependencies passed
[INFO]
[INFO] --- enforcer:3.5.0:enforce (enforce-java) @ jetty-ee10-bom ---
[INFO] Rule 3:
org.eclipse.jetty.toolchain.enforcer.rules.RequireOsgiCompatibleVersionRule(versionOsgiRule)
passed
[INFO] Rule 4:
org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps passed
[INFO]
[INFO] --- build-helper:3.6.0:parse-version (set-osgi-version) @
jetty-ee10-bom ---
[INFO]
[INFO] --- jacoco:0.8.13:prepare-agent (jacoco-initialize) @ jetty-ee10-bom
---
[INFO] argLine set to
-javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
[INFO]
[INFO] --- jacoco:0.8.13:prepare-agent (jacoco-setup-m-invoker-p) @
jetty-ee10-bom ---
[INFO] invoker.mavenOpts set to
-javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
[INFO]
[INFO] --- remote-resources:3.2.0:process (copy-shared-resources) @
jetty-ee10-bom ---
[INFO] Preparing remote bundle
org.eclipse.jetty:build-resources:12.0.22-SNAPSHOT
[INFO] Copying 0 resource from 1 bundle.
[INFO]
[INFO] --- jetty-version:2.7:attach-version-text (attach-version) @
jetty-ee10-bom ---
[INFO]
[INFO] --- resources:3.3.1:copy-resources (copy-resources) @ jetty-ee10-bom
---
[INFO] skip non existing resourceDirectory
/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/src/main/config
[INFO]
[INFO] --- flatten:1.7.0:flatten (flatten) @ jetty-ee10-bom ---
[INFO] Generating flattened POM of project
org.eclipse.jetty.ee10:jetty-ee10-bom:pom:12.0.22-SNAPSHOT...
[INFO]
[INFO] --- bundle:5.1.9:manifest (default) @ jetty-ee10-bom ---
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar,
maven-plugin]
[INFO]
[INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ jetty-ee10-bom ---
[INFO]
[INFO] --- jacoco:0.8.13:report (jacoco-site) @ jetty-ee10-bom ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- assembly:3.7.1:single (config-assembly) @ jetty-ee10-bom ---
[INFO] Mimir session closed (RETRIEVED=0 CACHED=0)
[ERROR] Failed to execute goal
org
Re: Maven 4.0.0 Release - Thoughts?
I used apache-maven-4.0.0-rc-3 btw. I would have a try at the latest github
code version...
Xeno Amess 于2025年5月29日周四 14:39写道：
> jetty is a good example.
> mvn3 can build but mvn4 cannot.
>
> maven-assembly-plugin:3.7.1 wrongly invoking a bom sub-project
>
> [INFO] ---< org.eclipse.jetty.ee10:jetty-ee10-bom
> >
> [INFO] Building EE10 :: BOM 12.0.22-SNAPSHOT
> [90/354]
> [INFO] from jetty-ee10/jetty-ee10-bom/pom.xml
> [INFO] [ pom
> ]-
> [INFO] Going to calculate checksum for project
> [groupId=org.eclipse.jetty.ee10, artifactId=jetty-ee10-bom,
> version=12.0.22-SNAPSHOT]
> [INFO] Project inputs calculated in 0 ms. XXMM checksum [7b7b6120251dfd1d]
> calculated in 0 ms.
> [INFO] Attempting to restore project org.eclipse.jetty.ee10:jetty-ee10-bom
> from build cache
> [INFO] Local build found by checksum 7b7b6120251dfd1d
> [INFO] Found cached build, restoring org.eclipse.jetty.ee10:jetty-ee10-bom
> from cache by checksum 7b7b6120251dfd1d
> [WARNING] Cached build doesn't contains all requested plugin executions
> (missing:
> [org.apache.maven.plugins:maven-resources-plugin:3.3.1:copy-resources
> {execution: copy-resources},
> org.apache.maven.plugins:maven-assembly-plugin:3.7.1:single {execution:
> config-assembly}]), cannot restore
> [INFO] Local build was not found by checksum 7b7b6120251dfd1d for
> org.eclipse.jetty.ee10:jetty-ee10-bom
> [INFO]
> [INFO] --- spotless:2.44.4:check (default) @ jetty-ee10-bom ---
> [INFO] Index file does not exist. Fallback to an empty index
> [INFO] Sorting file /tmp/pom11239457262347372795.xml
> [INFO] Pom file is already sorted, exiting
> [INFO] Spotless.Pom is keeping 1 files clean - 0 needs changes to be
> clean, 1 were already clean, 0 were skipped because caching determined they
> were already clean
> [INFO]
> [INFO] --- checkstyle:3.6.0:check (checkstyle-check) @ jetty-ee10-bom ---
> [INFO] 开始检查……
> 检查完成。
> [INFO] You have 0 Checkstyle violations.
> [INFO]
> [INFO] --- enforcer:3.5.0:enforce (ban-javax-servlet-api) @ jetty-ee10-bom
> ---
> [INFO] Rule 0:
> org.apache.maven.enforcer.rules.dependency.BannedDependencies passed
> [INFO]
> [INFO] --- enforcer:3.5.0:enforce (enforce-java) @ jetty-ee10-bom ---
> [INFO] Rule 3:
> org.eclipse.jetty.toolchain.enforcer.rules.RequireOsgiCompatibleVersionRule(versionOsgiRule)
> passed
> [INFO] Rule 4:
> org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps passed
> [INFO]
> [INFO] --- build-helper:3.6.0:parse-version (set-osgi-version) @
> jetty-ee10-bom ---
> [INFO]
> [INFO] --- jacoco:0.8.13:prepare-agent (jacoco-initialize) @
> jetty-ee10-bom ---
> [INFO] argLine set to
> -javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
> [INFO]
> [INFO] --- jacoco:0.8.13:prepare-agent (jacoco-setup-m-invoker-p) @
> jetty-ee10-bom ---
> [INFO] invoker.mavenOpts set to
> -javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
> [INFO]
> [INFO] --- remote-resources:3.2.0:process (copy-shared-resources) @
> jetty-ee10-bom ---
> [INFO] Preparing remote bundle
> org.eclipse.jetty:build-resources:12.0.22-SNAPSHOT
> [INFO] Copying 0 resource from 1 bundle.
> [INFO]
> [INFO] --- jetty-version:2.7:attach-version-text (attach-version) @
> jetty-ee10-bom ---
> [INFO]
> [INFO] --- resources:3.3.1:copy-resources (copy-resources) @
> jetty-ee10-bom ---
> [INFO] skip non existing resourceDirectory
> /home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/src/main/config
> [INFO]
> [INFO] --- flatten:1.7.0:flatten (flatten) @ jetty-ee10-bom ---
> [INFO] Generating flattened POM of project
> org.eclipse.jetty.ee10:jetty-ee10-bom:pom:12.0.22-SNAPSHOT...
> [INFO]
> [INFO] --- bundle:5.1.9:manifest (default) @ jetty-ee10-bom ---
> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar,
> maven-plugin]
> [INFO]
> [INFO] --- source:3.3.1:jar-no-fork (attach-sources) @ jetty-ee10-bom ---
Re: Maven 4.0.0 Release - Thoughts?
nope. neither can the github master latest.
Xeno Amess 于2025年5月29日周四 14:40写道：
> I used apache-maven-4.0.0-rc-3 btw. I would have a try at the latest
> github code version...
>
> Xeno Amess 于2025年5月29日周四 14:39写道：
>
>> jetty is a good example.
>> mvn3 can build but mvn4 cannot.
>>
>> maven-assembly-plugin:3.7.1 wrongly invoking a bom sub-project
>>
>> [INFO] ---< org.eclipse.jetty.ee10:jetty-ee10-bom
>> >
>> [INFO] Building EE10 :: BOM 12.0.22-SNAPSHOT
>> [90/354]
>> [INFO] from jetty-ee10/jetty-ee10-bom/pom.xml
>> [INFO] [ pom
>> ]-
>> [INFO] Going to calculate checksum for project
>> [groupId=org.eclipse.jetty.ee10, artifactId=jetty-ee10-bom,
>> version=12.0.22-SNAPSHOT]
>> [INFO] Project inputs calculated in 0 ms. XXMM checksum
>> [7b7b6120251dfd1d] calculated in 0 ms.
>> [INFO] Attempting to restore project
>> org.eclipse.jetty.ee10:jetty-ee10-bom from build cache
>> [INFO] Local build found by checksum 7b7b6120251dfd1d
>> [INFO] Found cached build, restoring
>> org.eclipse.jetty.ee10:jetty-ee10-bom from cache by checksum
>> 7b7b6120251dfd1d
>> [WARNING] Cached build doesn't contains all requested plugin executions
>> (missing:
>> [org.apache.maven.plugins:maven-resources-plugin:3.3.1:copy-resources
>> {execution: copy-resources},
>> org.apache.maven.plugins:maven-assembly-plugin:3.7.1:single {execution:
>> config-assembly}]), cannot restore
>> [INFO] Local build was not found by checksum 7b7b6120251dfd1d for
>> org.eclipse.jetty.ee10:jetty-ee10-bom
>> [INFO]
>> [INFO] --- spotless:2.44.4:check (default) @ jetty-ee10-bom ---
>> [INFO] Index file does not exist. Fallback to an empty index
>> [INFO] Sorting file /tmp/pom11239457262347372795.xml
>> [INFO] Pom file is already sorted, exiting
>> [INFO] Spotless.Pom is keeping 1 files clean - 0 needs changes to be
>> clean, 1 were already clean, 0 were skipped because caching determined they
>> were already clean
>> [INFO]
>> [INFO] --- checkstyle:3.6.0:check (checkstyle-check) @ jetty-ee10-bom ---
>> [INFO] 开始检查……
>> 检查完成。
>> [INFO] You have 0 Checkstyle violations.
>> [INFO]
>> [INFO] --- enforcer:3.5.0:enforce (ban-javax-servlet-api) @
>> jetty-ee10-bom ---
>> [INFO] Rule 0:
>> org.apache.maven.enforcer.rules.dependency.BannedDependencies passed
>> [INFO]
>> [INFO] --- enforcer:3.5.0:enforce (enforce-java) @ jetty-ee10-bom ---
>> [INFO] Rule 3:
>> org.eclipse.jetty.toolchain.enforcer.rules.RequireOsgiCompatibleVersionRule(versionOsgiRule)
>> passed
>> [INFO] Rule 4:
>> org.apache.maven.enforcer.rules.dependency.RequireUpperBoundDeps passed
>> [INFO]
>> [INFO] --- build-helper:3.6.0:parse-version (set-osgi-version) @
>> jetty-ee10-bom ---
>> [INFO]
>> [INFO] --- jacoco:0.8.13:prepare-agent (jacoco-initialize) @
>> jetty-ee10-bom ---
>> [INFO] argLine set to
>> -javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
>> [INFO]
>> [INFO] --- jacoco:0.8.13:prepare-agent (jacoco-setup-m-invoker-p) @
>> jetty-ee10-bom ---
>> [INFO] invoker.mavenOpts set to
>> -javaagent:/home/xenoamess/.m2/repository/org/jacoco/org.jacoco.agent/0.8.13/org.jacoco.agent-0.8.13-runtime.jar=destfile=/home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/target/jacoco.exec,excludes=**/org/eclipse/jetty/ant/**:*/org/eclipse/jetty/maven/its/**:**/org/eclipse/jetty/embedded/**:**/org/eclipse/jetty/asyncrest/**:**/org/eclipse/jetty/demo/**:**/org/eclipse/jetty/gcloud/**:**/org/eclipse/jetty/infinispan/**:**/org/eclipse/jetty/osgi/**:**/org/eclipse/jetty/spring/**:**/org/eclipse/jetty/http/spi/**:**/org/eclipse/jetty/tests/**:**/org/eclipse/jetty/test/**
>> [INFO]
>> [INFO] --- remote-resources:3.2.0:process (copy-shared-resources) @
>> jetty-ee10-bom ---
>> [INFO] Preparing remote bundle
>> org.eclipse.jetty:build-resources:12.0.22-SNAPSHOT
>> [INFO] Copying 0 resource from 1 bundle.
>> [INFO]
>> [INFO] --- jetty-version:2.7:attach-version-text (attach-version) @
>> jetty-ee10-bom ---
>> [INFO]
>> [INFO] --- resources:3.3.1:copy-resources (copy-resources) @
>> jetty-ee10-bom ---
>> [INFO] skip non existing resourceDirectory
>> /home/xenoamess/workspace/jetty.project/jetty-ee10/jetty-ee10-bom/src/main/config
>> [INFO]
>> [INFO] --- flatten:1.7.0:flatten (flatten) @ jetty-ee10-bom ---
>> [INFO] Generating flattened POM of project
>> org.eclipse.jetty.ee10:jetty-ee10-bom:pom:12.0.22-SNAPSHOT...
>> [INFO]
>> [INFO] --- bundle:5.1.9:manifest (default) @ jetty-ee1
Re: Maven 4.0.0 Release - Thoughts?
Hey, Delany. I will look into this. Also to avoid confusion let's continue this discussion in the proper thread as it's not related to maven 4 release On Wed, May 28, 2025 at 4:22 PM Delany wrote: > Hi Sergei, > > I'm running with this extension going forward. I don't use the build cache > (yet) so that's not an issue. > When trying to promote unit tests to a company that's resistant its helpful > to be able to say the tests won't slow down the build. > > We have one huge module though (project we're calling it now) with > extensive tests, and its a bottleneck for all that follow. > Typically we had to skip tests, but now we don't have to. Build time was > cut in half. > > I did notice jacoco coverage was disabled as I bound the > jacoco-maven-plugin report goal to the prepare-package phase. > As the documentation says, the phases have been switched around. > But can you make it work with the buildplan-maven-plugin:list-phases goal > so I can actually see which phases runs when, or is that up to this plugin > to figure out? > > Kind regards, > Delany > > > On Wed, 28 May 2025 at 14:55, Sergey Chernov > wrote: > > > Guillaume, that's awesome. It's good that there is no rush with it. > > Once I'll have insights, I'll share them. > > > > Xeno, the project I'm checking is private unfortunately. Also this can be > > quite challenging to find a good Maven multi-module project as a > reference > > for performance testing and compatibility validations, as many of big > > projects e.g. have flaky tests and other issues. > > Some of the biggest that I've seen: > > * https://github.com/quarkusio/quarkus (has lots of customizations in > > .mvn/extensions.xml) > > * https://github.com/apache/dubbo > > * https://github.com/apache/hadoop > > * https://github.com/apache/struts > > * https://github.com/vaadin/flow and https://github.com/vaadin/framework > > > > > > On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet > wrote: > > > > > After considering the concerns about API stability, plugin > > > compatibility, and the performance issues reported by Sergey (4x > > > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > > > should opt for an rc4 to address these issues. My proposal is to > > > release a final release candidate (rc4) soon, aiming for a General > > > Availability (GA) release in September. Post rc4, I suggest creating a > > > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > > > changes like records and sequenced collections, as well as new > > > features such as mixins, cascading profiles, server aliases, JDK 21 > > > (still under discussion) and more > > > > > > The recent API changes for JPMS, as Martin noted, only affect the > > > experimental API, so they shouldn’t block the release. On Matthias’s > > > suggestion, enabling GitHub Issues across all repositories before the > > > GA seems like a good idea to improve user feedback. Let’s focus on > > > stabilizing rc4 and addressing performance bottlenecks, possibly > > > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > > > > > What do you think about this plan? > > > > > > On a side note, I created a few months ago a project to check Maven 4 > > > compatibility with all Apache projects using Maven. The results for > > > RC-3 can be found at > > > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > > > errors are caused by the use of incompatible plugins (which needs to > > > be updated) or incorrect POMs (as Maven 4 is more strict about a few > > > things). What would be nice is a tool to integrate in the shell that > > > would fix those known incompatibilities, so that users would have an > > > easier migration path. And we could apply it to this project to make > > > more green boxes. > > > > > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a > > écrit : > > > > > > > > Hey Maven Devs, > > > > > > > > We're gearing up to release a new version from the master branch. I'm > > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > > Any > > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > > > Cheers, > > > > > > > > Guillaume > > > > > > > > > > > > > > > > > -- > > > > > > Guillaume Nodet > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > >
Re: Maven 4.0.0 Release - Thoughts?
I tested log4j2 an hour ago. on my computer mvn3 use 2:00(min), mvn4 use 1:53(min) no much difference. would try test your examples later. Sergey Chernov 于2025年5月28日周三 20:55写道： > Guillaume, that's awesome. It's good that there is no rush with it. > Once I'll have insights, I'll share them. > > Xeno, the project I'm checking is private unfortunately. Also this can be > quite challenging to find a good Maven multi-module project as a reference > for performance testing and compatibility validations, as many of big > projects e.g. have flaky tests and other issues. > Some of the biggest that I've seen: > * https://github.com/quarkusio/quarkus (has lots of customizations in > .mvn/extensions.xml) > * https://github.com/apache/dubbo > * https://github.com/apache/hadoop > * https://github.com/apache/struts > * https://github.com/vaadin/flow and https://github.com/vaadin/framework > > > On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet wrote: > > > After considering the concerns about API stability, plugin > > compatibility, and the performance issues reported by Sergey (4x > > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > > should opt for an rc4 to address these issues. My proposal is to > > release a final release candidate (rc4) soon, aiming for a General > > Availability (GA) release in September. Post rc4, I suggest creating a > > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > > changes like records and sequenced collections, as well as new > > features such as mixins, cascading profiles, server aliases, JDK 21 > > (still under discussion) and more > > > > The recent API changes for JPMS, as Martin noted, only affect the > > experimental API, so they shouldn’t block the release. On Matthias’s > > suggestion, enabling GitHub Issues across all repositories before the > > GA seems like a good idea to improve user feedback. Let’s focus on > > stabilizing rc4 and addressing performance bottlenecks, possibly > > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > > > What do you think about this plan? > > > > On a side note, I created a few months ago a project to check Maven 4 > > compatibility with all Apache projects using Maven. The results for > > RC-3 can be found at > > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > > errors are caused by the use of incompatible plugins (which needs to > > be updated) or incorrect POMs (as Maven 4 is more strict about a few > > things). What would be nice is a tool to integrate in the shell that > > would fix those known incompatibilities, so that users would have an > > easier migration path. And we could apply it to this project to make > > more green boxes. > > > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a > écrit : > > > > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > Cheers, > > > > > > Guillaume > > > > > > > > > > > > -- > > > > Guillaume Nodet > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: Maven 4.0.0 Release - Thoughts?
Guillaume, that's awesome. It's good that there is no rush with it. Once I'll have insights, I'll share them. Xeno, the project I'm checking is private unfortunately. Also this can be quite challenging to find a good Maven multi-module project as a reference for performance testing and compatibility validations, as many of big projects e.g. have flaky tests and other issues. Some of the biggest that I've seen: * https://github.com/quarkusio/quarkus (has lots of customizations in .mvn/extensions.xml) * https://github.com/apache/dubbo * https://github.com/apache/hadoop * https://github.com/apache/struts * https://github.com/vaadin/flow and https://github.com/vaadin/framework On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet wrote: > After considering the concerns about API stability, plugin > compatibility, and the performance issues reported by Sergey (4x > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > should opt for an rc4 to address these issues. My proposal is to > release a final release candidate (rc4) soon, aiming for a General > Availability (GA) release in September. Post rc4, I suggest creating a > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > changes like records and sequenced collections, as well as new > features such as mixins, cascading profiles, server aliases, JDK 21 > (still under discussion) and more > > The recent API changes for JPMS, as Martin noted, only affect the > experimental API, so they shouldn’t block the release. On Matthias’s > suggestion, enabling GitHub Issues across all repositories before the > GA seems like a good idea to improve user feedback. Let’s focus on > stabilizing rc4 and addressing performance bottlenecks, possibly > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > What do you think about this plan? > > On a side note, I created a few months ago a project to check Maven 4 > compatibility with all Apache projects using Maven. The results for > RC-3 can be found at > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > errors are caused by the use of incompatible plugins (which needs to > be updated) or incorrect POMs (as Maven 4 is more strict about a few > things). What would be nice is a tool to integrate in the shell that > would fix those known incompatibilities, so that users would have an > easier migration path. And we could apply it to this project to make > more green boxes. > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a écrit : > > > > Hey Maven Devs, > > > > We're gearing up to release a new version from the master branch. I'm > thinking we should go for 4.0.0 instead of rc-4. What do you all think? Any > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > Cheers, > > > > Guillaume > > > > > > > -- > > Guillaume Nodet > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Maven 4.0.0 Release - Thoughts?
Jetty is a good one as well: https://github.com/jetty/jetty.project Gary On Wed, May 28, 2025, 08:55 Sergey Chernov wrote: > Guillaume, that's awesome. It's good that there is no rush with it. > Once I'll have insights, I'll share them. > > Xeno, the project I'm checking is private unfortunately. Also this can be > quite challenging to find a good Maven multi-module project as a reference > for performance testing and compatibility validations, as many of big > projects e.g. have flaky tests and other issues. > Some of the biggest that I've seen: > * https://github.com/quarkusio/quarkus (has lots of customizations in > .mvn/extensions.xml) > * https://github.com/apache/dubbo > * https://github.com/apache/hadoop > * https://github.com/apache/struts > * https://github.com/vaadin/flow and https://github.com/vaadin/framework > > > On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet wrote: > > > After considering the concerns about API stability, plugin > > compatibility, and the performance issues reported by Sergey (4x > > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > > should opt for an rc4 to address these issues. My proposal is to > > release a final release candidate (rc4) soon, aiming for a General > > Availability (GA) release in September. Post rc4, I suggest creating a > > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > > changes like records and sequenced collections, as well as new > > features such as mixins, cascading profiles, server aliases, JDK 21 > > (still under discussion) and more > > > > The recent API changes for JPMS, as Martin noted, only affect the > > experimental API, so they shouldn’t block the release. On Matthias’s > > suggestion, enabling GitHub Issues across all repositories before the > > GA seems like a good idea to improve user feedback. Let’s focus on > > stabilizing rc4 and addressing performance bottlenecks, possibly > > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > > > What do you think about this plan? > > > > On a side note, I created a few months ago a project to check Maven 4 > > compatibility with all Apache projects using Maven. The results for > > RC-3 can be found at > > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > > errors are caused by the use of incompatible plugins (which needs to > > be updated) or incorrect POMs (as Maven 4 is more strict about a few > > things). What would be nice is a tool to integrate in the shell that > > would fix those known incompatibilities, so that users would have an > > easier migration path. And we could apply it to this project to make > > more green boxes. > > > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a > écrit : > > > > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > Cheers, > > > > > > Guillaume > > > > > > > > > > > > -- > > > > Guillaume Nodet > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: Maven 4.0.0 Release - Thoughts?
Hi Sergei, I'm running with this extension going forward. I don't use the build cache (yet) so that's not an issue. When trying to promote unit tests to a company that's resistant its helpful to be able to say the tests won't slow down the build. We have one huge module though (project we're calling it now) with extensive tests, and its a bottleneck for all that follow. Typically we had to skip tests, but now we don't have to. Build time was cut in half. I did notice jacoco coverage was disabled as I bound the jacoco-maven-plugin report goal to the prepare-package phase. As the documentation says, the phases have been switched around. But can you make it work with the buildplan-maven-plugin:list-phases goal so I can actually see which phases runs when, or is that up to this plugin to figure out? Kind regards, Delany On Wed, 28 May 2025 at 14:55, Sergey Chernov wrote: > Guillaume, that's awesome. It's good that there is no rush with it. > Once I'll have insights, I'll share them. > > Xeno, the project I'm checking is private unfortunately. Also this can be > quite challenging to find a good Maven multi-module project as a reference > for performance testing and compatibility validations, as many of big > projects e.g. have flaky tests and other issues. > Some of the biggest that I've seen: > * https://github.com/quarkusio/quarkus (has lots of customizations in > .mvn/extensions.xml) > * https://github.com/apache/dubbo > * https://github.com/apache/hadoop > * https://github.com/apache/struts > * https://github.com/vaadin/flow and https://github.com/vaadin/framework > > > On Wed, May 28, 2025 at 2:16 PM Guillaume Nodet wrote: > > > After considering the concerns about API stability, plugin > > compatibility, and the performance issues reported by Sergey (4x > > slower in rc3), I agree with Sylwester, Benjamin, and Elliotte that we > > should opt for an rc4 to address these issues. My proposal is to > > release a final release candidate (rc4) soon, aiming for a General > > Availability (GA) release in September. Post rc4, I suggest creating a > > 4.0.x branch to start work on 4.1.0. For 4.1.0, we could introduce API > > changes like records and sequenced collections, as well as new > > features such as mixins, cascading profiles, server aliases, JDK 21 > > (still under discussion) and more > > > > The recent API changes for JPMS, as Martin noted, only affect the > > experimental API, so they shouldn’t block the release. On Matthias’s > > suggestion, enabling GitHub Issues across all repositories before the > > GA seems like a good idea to improve user feedback. Let’s focus on > > stabilizing rc4 and addressing performance bottlenecks, possibly > > exploring Martin’s O(N²) concerns with profiling, as Sergey offered. > > > > What do you think about this plan? > > > > On a side note, I created a few months ago a project to check Maven 4 > > compatibility with all Apache projects using Maven. The results for > > RC-3 can be found at > > https://github.com/gnodet/maven4-testing/issues/2812. Most of the > > errors are caused by the use of incompatible plugins (which needs to > > be updated) or incorrect POMs (as Maven 4 is more strict about a few > > things). What would be nice is a tool to integrate in the shell that > > would fix those known incompatibilities, so that users would have an > > easier migration path. And we could apply it to this project to make > > more green boxes. > > > > Le mer. 21 mai 2025 à 08:11, Guillaume Nodet a > écrit : > > > > > > Hey Maven Devs, > > > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? > Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > > > Cheers, > > > > > > Guillaume > > > > > > > > > > > > -- > > > > Guillaume Nodet > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
Re: [VOTE] Release Apache Maven Clean Plugin version 3.5.0
+1 (nb) Am 28.05.2025 um 00:20 schrieb Slawomir Jaranowski: Hi, We solved 6 issues: https://github.com/apache/maven-clean-plugin/milestone/5?closed=1 There are still a couple of issues left: https://github.com/apache/maven-clean-plugin/issues Changes since the last release: https://github.com/apache/maven-clean-plugin/compare/maven-clean-plugin-3.4.1...maven-clean-plugin-3.5.0 Staging repo: https://repository.apache.org/content/repositories/maven-2292/ https://repository.apache.org/content/repositories/maven-2292/org/apache/maven/plugins/maven-clean-plugin/3.5.0/maven-clean-plugin-3.5.0-source-release.zip Source release checksum(s): maven-clean-plugin-3.5.0-source-release.zip - SHA-512 : ce4b6c59ff2efa9312b2c607507efb015d1caf5f21cdb09c92ce4eea751cf2b586c9984532d3788ffedae1a544f806524ab99540dab7b2252322ae8f94380d21 Staging site: https://maven.apache.org/plugins-archives/maven-clean-plugin-LATEST/ NOTE - site build with local patch: https://github.com/apache/maven-clean-plugin/pull/255 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
