Le mardi 14 janvier 2025, 09:25:55 CET Julien Plissonneau Duquène a écrit : > Le 2025-01-13 22:23, Gerd Aschemann a écrit : > > Additionally, I wonder about the technical implementation. Keeping them > > in one repo on separate branches makes using `repo` real hard. > > Could we at least combine them on a single branch? They could have > > separate subdirectories, or even a common reactor if it helps. > > New studies could still be developed on separate branches. But they > > should then be merged to the common `main` (`master` seems to be > > politically incorrect these days) if they mature. > > Seconding this. Unrelated branches make it unnecessarily complicated to > discover and build the projects in that repository.
yes when it is production code but here, remember, it is a replacement for sandbox that we had in svn, where temporary tests were light creating new Git repos, that are first class citizen and never deleted, is just heavy: notice that iin the past, when I created this, archived Git repositories (at GitHub and ASF) was not yet a thing as they are today I still find that lately, we had many maven-* Git repositories created for posterity that are just unmaintained = what this sandbox/study approach is trying to avoid For now, the key change to do is on adding these sandbox project to full aggregator build or not: build profile is the right step --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
