Thanks for your reply, Herve. You say "there is one target/*.buildinfo per module (listing all files for one gav)" and I'm a little confused. Does that mean if two modules have the same gav, will there be target/*.buildinfo files in both modules or only in one of them.
I've got my builds running on several multi-module maven builds and all but one end up with only a single target/*.buildinfo. My build process actually looks in all the <module> folders for the buildinfo files and logs wherever it finds one. That buildinfo contains references to all the submodule artifacts published plus #0 for the base pom (where the build starts). But, there is an exception and one build, multi-module build, generates two target/*.buildinfo. One is in the target folder in the same folder as the base pom (where the build starts) and one is in the last module folder that builds (according to what the build logs show as to module ordering). In this case, both buildinfo files seem to have references to files published from 19 sub-modules and a pom published from that base folder (where the starting pom is). Anyway, thanks for your answer and I hope you can dispel some of my confusion about what you meant about "one per module" and "one gav". Thanks Lee On Wed, Sep 3, 2025 at 9:14 AM Hervé Boutemy <hbout...@apache.org> wrote: > thanks Tamas for reminding me :) > > there is one target/*.buildinfo per module (listing all files for one gav) > and there is one for aggregate, in one of the modules > or perhaps even in 2 modules: the last one and the root one, because I > implemented the feature step by step and I kept each step output as it is > temporary data in target dir > > Regards, > > Hervé > > On 2025/08/26 16:53:19 Lee Meador wrote: > > What I read about using maven-artifact-plugin (reproducible builds) says > it > > will generate a single buildinfo file but I have one of my maven > > multimodule builds that generates 2. > > > > Does anyone know why there is more than one buildinfo file. > > > > The logs look like this showing "Saved aggregate info on build" to one > file > > (in the folder for the last of the submodules built) and then "Aggregate > > buildinfo copied" to another file (in the folder with the base pom -- the > > pom with the <module> tag in it: > > > > 2025-08-25T20:51:20.2852156Z [INFO] Saved aggregate info on build to > > > /home/runner/work/my_company_web_services/my_company_web_services/my_company_webservices/session_close_client/target/my_company_ws_session_close_client-4.0.8-1ff00d1d.buildinfo > > 2025-08-25T20:51:20.2856358Z [INFO] Aggregate buildinfo copied to > > > /home/runner/work/my_company_web_services/my_company_web_services/target/my_company_web_services-4.0.8-1ff00d1d.buildinfo > > 2025-08-25T20:51:20.2860141Z [INFO] Attaching buildinfo > > 2025-08-25T20:51:20.2863240Z [INFO] > > ------------------------------------------------------------------------ > > 2025-08-25T20:51:20.2864099Z [INFO] Reactor Summary for > > my_company_web_services 4.0.8-1ff00d1d: > > > > I haven't compared the two buildinfo files byte by byte but both show all > > 20 submodules and the 3 output files for each (pom, jar and > -classifier.jar) > > > > Can anyone explain why? > > > > -- Lee Meador > > Sent from gmail. My real email address is lee AT leemeador.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
