And, as I commented in https://cwiki.apache.org/confluence/display/MAVEN/Scheme+for+managing+Maven+source+in+Git, I think we're perfectly happy just to keep the current module structure. There may be some opportunities related to changing it, but I think most of us can agree on just keeping up the existing top-level modules. (Some of the current asf git clones are not good, but that's a different issue)
So at the end of the day, most of this discussion is really about if we can be even smarter ;) And sorry for insulting cvs users out there, I feel your pain. Kristian 2012/9/6 Kristian Rosenvold <kristian.rosenv...@gmail.com>: > 2012/9/6 Chris Graham <chrisgw...@gmail.com>: >> The fact that a lot of people have said +1 and there are still discussions >> around how to best set up a repo, means to me, that there is lots more room >> for dissussion. > > We have a hundred projects or more ;) A substantial group of people > here have been through extensive git migrations, so we know the basic moves. > I know it can be hard to distinguish when we're discussing nitty-gritty > details > from hugely important issues, since most of the time we're not being very > clear > about this (and we always discuss as if it's vitally important ;). > > I think it's safe to expect that we'll be going through a few > alternatives for some > of the projects. And migrating everything is probably a quite long story. > > Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
