Hi all, Install by default locally is probably OK for devs, especially for multi-module projects, but deploy by default is a bad IMO: I often work in one repo and install, then switch to another repo and test the new snapshot jars. Round and round until my changes are fully baked. This usually means having 2 Eclipse instances open at the same time, we have some projects with lots of modules. Deploying by default adds time and inflicts my work in progress on everyone else. I'm sure I'd turn that off.
I would turn off both for sure in GitHub CI builds, so hopefully that can be turned off on the command line so I don't have to make my POMs even more complicated ;-) An otherwise happy Maven user giving up 2c, Gary On Fri, Jun 14, 2024, 12:15 PM Tamás Cservenák <ta...@cservenak.net> wrote: > Howdy, > > As history proved, the original "interleaved" install/deploy is just call > for problems, and causes in need for circumventions like > https://issues.apache.org/jira/browse/MNG-8054 to make classic "snapshot > TS > lock-down" possible on large(r) projects. Also, no wonder our users were > asking for this feature for a quite long time. > > Hence, I'd propose that in upcoming releases (ie 3.2.0 of them), in plugins > m-install-p and m-deploy-p simply "flip" the defaults: and make them > install/deploy At End by default, while keeping the ability to "reverse" if > someone really depends on per-module deploys. > > WDYT? > > Thanks > T >
