On Fri, May 6, 2022 at 12:29 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> Howdy, > > no, not my memory, I rely on my "daily routine": I use Maven Repository > Manager, I regularly nuke my local repo, regularly execute `git clean -fdx` > on my checkout, and on checkout/branch change regularly do "quick-build" > `mvn clean install` (usually `mvn clean install -Dtest=void`) as very first > step. Have to add, I tend to work on projects that finish these "quick > builds" in a matter of minutes at most, not hours :) This "process" works > for me just fine. > Fwiw, my "daily routine" with That Other Build Tool is to just ask it to build and let it handle everything for me: never need to clean (through git clean or the clean task), never need to nuke my local cache because it really only includes remote artifacts and I never need to use SNAPSHOTs (again, because everything can be built in the same invocation without the need to split things in separate "projects" –like you suggested for the extension or even annotation processor–, so I never need to 'install' things locally, or deploy snapshots to a repository), and never need to do "quick-builds" either. I ask it to build, it builds what it needs to build, everything Just Works™. It also has accurate incremental builds, and even a (local or remote, I only use local) build cache so things don't necessarily have to be rebuilt when I switch between branches. This is what I expect from any build tool, and we even start to see such things coming to Node/NPM! > But, now that you bring up topic of "branched development", something I > always hated for very same reason you bring up, I think you will be happy > to see upcoming changes: > > > https://github.com/apache/maven-resolver/blob/master/src/site/markdown/local-repository.md > > (unreleased yet, we plan this for Resolver 1.8.1 and Maven 3.9.0). > > All in all I think we both agree, but still: Maven as a project is big > (huge actually), and volunteers working on it have hard time to catch up, > Indeed it's a shame that the project is so underfunded given the many wealthy companies relying on it! For my part, I try to avoid Maven if I can, except possibly for very simple builds. I still have to work with Maven in some projects, I maintain some Maven plugin and archetypes, and have to deal with Maven as a consumer of libraries I contribute to (lately having to make tests with artifact relocation and BOMs) Am not saying either "maven is the best", but I am convinced "maven can be > better", MUCH better and we will do it. As a matter of fact, we are already > doing it, step by step, baby steps :) > Yes, and Maven 4 has some good things coming! -- Thomas Broyer /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
