Re: Maven 4 performances problems

I've raised a PR for review https://github.com/apache/maven/pull/486/ This kina rewrites the build/consumer transformation to reuse the xml pull parser and do the transformation on the fly instead of reading and transforming with a sax api and writing to a stream so that the pull parser can

Re: Maven 4 performances problems

+1 to fix it before any > alpha release but also agree it is fine to let the alpha-1 go out while it is explicitly mentionned as known and under work. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: Maven 4 performances problems

Am 2021-07-01 um 11:19 schrieb Guillaume Nodet: I've been running a few tests to measure performances. This simplistic test looks like running the following command in a loop and measure the execution time. This is done on a quite big project so that a bunch of pom files are actually read. for

Re: Maven 4 performances problems

No, I don't think this requires a delay in the alpha-1 release. Le jeu. 1 juil. 2021 à 12:27, Robert Scholte a écrit : > Should we postpone the alpha-1 release because of this? > For me the most important reason for alpha-1 is to get confirmation that > builds won't be broken due to

Re: Maven 4 performances problems

I agree. We could even mention this known performance "issue" so there wouldn't be any surprise. /Anders On Thu, Jul 1, 2021 at 12:29 PM Enrico Olivelli wrote: > Il giorno gio 1 lug 2021 alle ore 12:27 Robert Scholte < > rfscho...@apache.org> > ha scritto: > > > Should we postpone the alpha-1

Re: Maven 4 performances problems

Il giorno gio 1 lug 2021 alle ore 12:27 Robert Scholte ha scritto: > Should we postpone the alpha-1 release because of this? > For me the most important reason for alpha-1 is to get confirmation that > builds won't be broken due to build/consumer. > 100% agreed it is an ALPHA and there are many

Re: Maven 4 performances problems

Should we postpone the alpha-1 release because of this? For me the most important reason for alpha-1 is to get confirmation that builds won't be broken due to build/consumer. But if users simply look at buildtime and due to some slower result don't care for the other changes, then we shouldn't

Maven 4 performances problems

I've been running a few tests to measure performances. This simplistic test looks like running the following command in a loop and measure the execution time. This is done on a quite big project so that a bunch of pom files are actually read. for i in 1 2 3 4 5 6 7 8 9 10 ; do time