Re: Multi-repo experience

lhd1h2k8r5lzydf2g>. If >> you >> have any feedback, I would be more than happy to hear. >> >> On Sat, Aug 26, 2023 at 2:03 PM Hervé Boutemy >> wrote: >> >> > notice that you call it "multi-repo experience" >> > it's i

Re: Multi-repo experience

gt;. If you > have any feedback, I would be more than happy to hear. > > On Sat, Aug 26, 2023 at 2:03 PM Hervé Boutemy > wrote: > > > notice that you call it "multi-repo experience" > > it's in fact more about a topic of component-oriented structure, each &g

Re: Multi-repo experience

lt;https://lists.apache.org/thread/9mz47opyjwtf15ylhd1h2k8r5lzydf2g>. If you have any feedback, I would be more than happy to hear. On Sat, Aug 26, 2023 at 2:03 PM Hervé Boutemy wrote: > notice that you call it "multi-repo experience" > it's in fact more about a topic of co

Re: Multi-repo experience

others. Le sam. 26 août 2023 à 16:03, Hervé Boutemy a écrit : > notice that you call it "multi-repo experience" > it's in fact more about a topic of component-oriented structure, each > component having its own release lifecycle. The fact that each component > has > his

Re: Multi-repo experience

notice that you call it "multi-repo experience" it's in fact more about a topic of component-oriented structure, each component having its own release lifecycle. The fact that each component has his own Git repository is just an implementation detail (in the past, each compon

Re: Multi-repo experience

Hi Volkan, Yes, I worked a lot on this aspect fo Maven: the result is summarised here https://maven.apache.org/scm.html As you can see, you can get "Maven Full Sources" in one command using Google "repo" tool. Please have a llok and we can dive into more details if you need Regards, Hervé Le

Re: Multi-repo experience

OK, ignore me, you're talking about the other way. On Thu, Aug 24, 2023 at 1:27 PM Paul Hammant wrote: > A classic pom.xml at root in a single repo, then multiple levels of child > directory each with its own pom.xml (and its own src/main/java & > src.test/java) ? > > Branching model would be tr

Re: Multi-repo experience

A classic pom.xml at root in a single repo, then multiple levels of child directory each with its own pom.xml (and its own src/main/java & src.test/java) ? Branching model would be trunk based development (and branch for release), possibly as short-lived feature branches in the GitHub Pull-Request

Multi-repo experience

Hello, Log4j crew is considering moving to a multi-repo structure. If I am not mistaken, there are 125 `github.com/apache/maven-*` repos, which makes me believe that you have quite a bit of experience with such a construct. I am curious to hear your thoughts on t