Update on issue I'm facing. The issue is using the site:jar during the release process. Rather than deploy site to any location, we jar it and deploy it with normal artifacts to Artifactory. Since that plugin goal wants the full build (aggregate), it fails against numerous plugins such as javadoc, jxr, etc. I presume rather than that running during package phase, it needs to be moved and run separately like how the site-deploy works with the release plugin. Any ideas on best way to deal with this? Right now it feels like its done in the right place, we even skip the 'site-deploy' entirely. But clearly that isn't exactly good enough in this case.
I don't think now that this is a maven 3.9.0 issue itself. I think its more of something that is a big change in this specific use case that just needs some direction to resolve. The more and more I've looked at this the more I've found little things that have changed over the years that had resulted in multiple site runs and some plugins from running exactly where expected. So this has been a hugely beneficial effort for us and just need to figure this last bit out. My next steps are to look more deeply into release plugin and how the site-deploy is actually working as that seems like I want to mimic that behaviour. Thanks, Jeremy -----Original Message----- From: Jeremy Landis <jeremylan...@hotmail.com> Sent: Wednesday, February 22, 2023 12:30 PM To: Maven Developers List <dev@maven.apache.org> Subject: RE: [HEADS UP] Maven Release 3.9.1 coming soon Hi Tomas, Will get back to you on ability to collect that data, lots of hoops to do so. It may be easier I just build sample project. On the cache, thanks for calling that out as not maven. It was gradle enterprise maven extension. I turned it off to rule it out and behaviour is the same just without any mention of the cache. I even tried to checkout the release tag and perform full build before running perform but that just failed with issues running install plugin during release:perform. So, I backed off to what is focus... To focus more on the site is the problem, I tried numerous attempts to make it stop running but couldn't get that to stick so I went into the cached parent used and set skip directly then ran release:perform again. It worked doing that. So on the aggregator behaviour change. Assuming then pre 3.9.0, when site plugins encountered and forked, if it was not already built it would build all? That seems to be the problem...which would make sense why a single module project does not encounter this at all. Thanks, Jeremy -----Original Message----- From: Tamás Cservenák <ta...@cservenak.net> Sent: Wednesday, February 22, 2023 10:35 AM To: Maven Developers List <dev@maven.apache.org> Subject: Re: [HEADS UP] Maven Release 3.9.1 coming soon Howdy, Wow, there are a lot of moving parts.... release plugin, site (within release?)... Do you use any 3rd party extension maybe? (unsure what build cache is in the realm of Maven 3.8.x, that works for you). But my first guess is a change in aggregator behaviour (pre 3.9.0 it was building ALL, in 3.9.0 it builds only what is aggregated). Ideally we'd really need a reproducer, and possibly some logs/outputs of what is actually happening here... If possible, and allowed, you can send me privately a ZIP of logs, and will handle it discreetly. Thanks T On Wed, Feb 22, 2023 at 4:27 PM Jeremy Landis <jeremylan...@hotmail.com> wrote: > I don't have a sharable example at the moment to show but hope enough > information here can spot the issue from one I just ran. If any > details missing, I can quickly apply more info. > > On multi module build, this is the steps. > > mvn release:clean -> ok > mvn release:prepare -> ok > mvn release:perform -> fails > > Failure is that it tries to run the maven-site-plugin at what seems > the immediate start of the process. These phases run... > > 1/3 -> perform:verify-completed-prepare-phases > 2/3 -> perform:checkout-project-from-scm > 3/3 -> perform:run-perform-goals > > First goal ran 'deploy site-deploy' > > Gets a warning: This build will only read from the build cache, since > the clean lifecycle is not part of the build invocation. > > That seems suspect given its just checked it out so how can it use > build cache there? I did try a subsequent mvn clean release:perform > which got through that, threw lots of enforcer errors for missing > parts, then back to trying to run the site and same failure. > > The failure is that it didn't even build the product. So site plugin > gets error that the artifacts for the release version don't exist. > > All maven release plugin settings involved otherwise > > - addSchema set to false > - arguments -Daether.checksums.algorithms=SHA-512,SHA-256,SHA-1, MD5 > - autoVersionSubmodules set to true > - release profiles as release | sign > > Our release profile simply does this > > - skip versions plugin > - skip dependency check plugin > - skip license plugin > - skip site deploy (strange that its doing site-deploy when we told it > not to). Executions on site are attach-descriptor, site, and jar. We > do not deploy to a site but we do release the jar of the site content. > - javadocs run as goal jar, test-jar (with a skip on earlier general > runs we do for checking) > - jar plugin we run test-jar > - source plugin we run jar-no-fork and test-jar-no-fork > > Our sign profile > > - Runs sign goal of gpg plugin > > Versions involved > > - site 3.12.1 > - release plugin version 3.0.0-M7 > > All our plugins are up to date as of 12/21/2022. > > I know having a real life one to test with would be easier and I can > work on getting one together for that purpose but hoping its something > obvious that rings some bells as to why the behaviour is that way. > > Thanks, > > Jeremy Landis > > > -----Original Message----- > From: Jeremy Landis <jeremylan...@hotmail.com> > Sent: Monday, February 20, 2023 11:32 AM > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: [HEADS UP] Maven Release 3.9.1 coming soon > > Not yet. I'll work on getting that together. For now we easily > enough drop back to 3.8.7 in those cases as we exclusively use the maven > wrapper. > So it has not been super critical for us yet. > > Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for > Android< > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.m > %2F&data=05%7C01%7C%7C38078fe04d1745907d2c08db14fa928b%7C84df9e7fe9f64 > 0afb435aaaaaaaaaaaa%7C1%7C0%7C638126838659128507%7CUnknown%7CTWFpbGZsb > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D% > 7C3000%7C%7C%7C&sdata=1ez%2FO1FG83EedDDOAOKH%2F7WRgdeTlk%2FzhNNs%2FPyI > zU0%3D&reserved=0 > s%2FAAb9ysg&data=05%7C01%7C%7Cac0932a0f8894084199108db14ea9e31%7C84df9 > e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638126770148896334%7CUnknown%7CT > WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > 6Mn0%3D%7C3000%7C%7C%7C&sdata=s0JMIe9HS65g48CFbjJNBFvqKC%2F6NhA2SPrUvN > p0wA0%3D&reserved=0 > > > ________________________________ > From: Tamás Cservenák <ta...@cservenak.net> > Sent: Monday, February 20, 2023 11:24:58 AM > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: [HEADS UP] Maven Release 3.9.1 coming soon > > Jeremy, > > Any specifics about the problems you face? And ideally a reproducer? > > Thanks > T > > On Mon, Feb 20, 2023, 17:21 Jeremy Landis <jeremylan...@hotmail.com> > wrote: > > > We have been unable to release multi module builds with maven 3 9.0. > > It seems the site has major problems trying to resolve the build > artifacts. > > Has this been reported yet or do any of the resolver items fix that? > > Single module releases using identical configuration release fine. > > > > Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for > > Android<https://na01.safelinks.protection.outlook.com/?url=https%3A% > > 2F > > %2Faka.ms%2FAAb9ysg&data=05%7C01%7C%7C837778bb457f4545139b08db136002 > > 1c > > %7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125075294386839%7CU > > nk > > nown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha > > Ww > > iLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FQBCk13PtoUsObKw6L2O4ocrWqjj > > zd > > b0kKWMpHdU54M%3D&reserved=0> > > ________________________________ > > From: Elliotte Rusty Harold <elh...@ibiblio.org> > > Sent: Monday, February 20, 2023 9:52:44 AM > > To: Maven Developers List <dev@maven.apache.org> > > Subject: Re: [HEADS UP] Maven Release 3.9.1 coming soon > > > > IMHO MNG-7700 and MNG-7701 are blockers. MNG-7704 is not a blocker. > > MNG-7703 I'm not sure of, but probably not. > > > > On Mon, Feb 20, 2023 at 12:05 PM Michael Osipov > > <micha...@apache.org> > > wrote: > > > > > > Am 2023-02-20 um 12:40 schrieb Tamás Cservenák: > > > > Howdy, > > > > > > > > The release of Maven 3.9.1, if nothing unexpected comes up, is > > > > to > > happen > > > > around next week (most of the issues will be fixed once resolver > > > > upped > > to > > > > newly released 1.9.5): > > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiss > > %2F&data=05%7C01%7C%7C38078fe04d1745907d2c08db14fa928b%7C84df9e7fe9f > > 640afb435aaaaaaaaaaaa%7C1%7C0%7C638126838659128507%7CUnknown%7CTWFpb > > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > > n0%3D%7C3000%7C%7C%7C&sdata=aDc5vRv%2BcSAZO378kvalmHP2NNAnNkbt48f1dx > > BSMSQ%3D&reserved=0 > > ue%2F&data=05%7C01%7C%7Cac0932a0f8894084199108db14ea9e31%7C84df9e7fe > > 9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638126770148896334%7CUnknown%7CTWF > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > 6Mn0%3D%7C3000%7C%7C%7C&sdata=X5CVt7rFghw87uzkRoJ0xYAETxx9yxeY8Dfmoj > > pt9jw%3D&reserved=0 > > s.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520MNG%25 > > 20 > > AND%2520fixVersion%2520%253D%25203.9.1&data=05%7C01%7C%7C837778bb457 > > f4 > > 545139b08db1360021c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638 > > 12 > > 5075294386839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2 > > lu > > MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sPUF4zeBsSM > > 4K > > Y4mS3pa17bbvi6AtFMoKZIheb7Ngpg%3D&reserved=0 > > > > > > > > Notable fixes > > > > - The 10% slowness is gone (introduced with 3.9.0) > > > > - The endless loops with webjars is fixed (long time existing > > > > issue) > > > > - The IAEx with sha1-like (hex) versions is fixed (long time > > > > existing > > issue) > > > > > > This release would be incomplete: > > > > > > * This must be fixed: > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiss > > %2F&data=05%7C01%7C%7C38078fe04d1745907d2c08db14fa928b%7C84df9e7fe9f > > 640afb435aaaaaaaaaaaa%7C1%7C0%7C638126838659128507%7CUnknown%7CTWFpb > > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > > n0%3D%7C3000%7C%7C%7C&sdata=aDc5vRv%2BcSAZO378kvalmHP2NNAnNkbt48f1dx > > BSMSQ%3D&reserved=0 > > ue%2F&data=05%7C01%7C%7Cac0932a0f8894084199108db14ea9e31%7C84df9e7fe > > 9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638126770148896334%7CUnknown%7CTWF > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > 6Mn0%3D%7C3000%7C%7C%7C&sdata=X5CVt7rFghw87uzkRoJ0xYAETxx9yxeY8Dfmoj > > pt9jw%3D&reserved=0 > > s.apache.org%2Fjira%2Fbrowse%2FMNG-7679&data=05%7C01%7C%7C837778bb45 > > 7f > > 4545139b08db1360021c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63 > > 81 > > 25075294386839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > > 2l > > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jskDY4aC8k > > 0U > > LFtCYmfTLagy9FVxiUSNoVZ62tdT1i4%3D&reserved=0 > > > * These two need to be discussed whether some action is needed: > > > ** > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiss > > %2F&data=05%7C01%7C%7C38078fe04d1745907d2c08db14fa928b%7C84df9e7fe9f > > 640afb435aaaaaaaaaaaa%7C1%7C0%7C638126838659128507%7CUnknown%7CTWFpb > > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > > n0%3D%7C3000%7C%7C%7C&sdata=aDc5vRv%2BcSAZO378kvalmHP2NNAnNkbt48f1dx > > BSMSQ%3D&reserved=0 > > ue%2F&data=05%7C01%7C%7Cac0932a0f8894084199108db14ea9e31%7C84df9e7fe > > 9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638126770148896334%7CUnknown%7CTWF > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > 6Mn0%3D%7C3000%7C%7C%7C&sdata=X5CVt7rFghw87uzkRoJ0xYAETxx9yxeY8Dfmoj > > pt9jw%3D&reserved=0 > > s.apache.org%2Fjira%2Fbrowse%2FMNG-7700&data=05%7C01%7C%7C837778bb45 > > 7f > > 4545139b08db1360021c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63 > > 81 > > 25075294386839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > > 2l > > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=unjbDFuKBr > > ZE > > azJZXnw0Ttq%2FxpKZNjLjLJHjkyuUbfI%3D&reserved=0 > > > ** > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fiss > > %2F&data=05%7C01%7C%7C38078fe04d1745907d2c08db14fa928b%7C84df9e7fe9f > > 640afb435aaaaaaaaaaaa%7C1%7C0%7C638126838659128507%7CUnknown%7CTWFpb > > GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6M > > n0%3D%7C3000%7C%7C%7C&sdata=aDc5vRv%2BcSAZO378kvalmHP2NNAnNkbt48f1dx > > BSMSQ%3D&reserved=0 > > ue%2F&data=05%7C01%7C%7Cac0932a0f8894084199108db14ea9e31%7C84df9e7fe > > 9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638126770148896334%7CUnknown%7CTWF > > pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI > > 6Mn0%3D%7C3000%7C%7C%7C&sdata=X5CVt7rFghw87uzkRoJ0xYAETxx9yxeY8Dfmoj > > pt9jw%3D&reserved=0 > > s.apache.org%2Fjira%2Fbrowse%2FMNG-7701&data=05%7C01%7C%7C837778bb45 > > 7f > > 4545139b08db1360021c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C63 > > 81 > > 25075294386839%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > > 2l > > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=68QR2cIpXP > > uI > > PLD%2BpSsTvrU3BfOKD2N4bgtro6Ag9Fk%3D&reserved=0 > > > > > > M > > > > > > > > > -- > > 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 > > > > > > --------------------------------------------------------------------- > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
