Yes, it sounded like that. Switching the entire "root"/repo to Git was also an option, a more drastic one of course than gradually doing this on a module per module basis.
We have a few differences in Maven artifactID and the folder name, e.g. /trunk contains a pom.xml called something like "devicemap-reactor" so I'd say we can try to harmonize some of these folder names, but unless e.g. a Git sync of exactly that sub-module (like "java", for "examples" it should be pretty much the same for most modules) makes it appealing, I don't see it as the highest priority. Nobody would suggest calling the parent POM just "trunk" though under "org.apache.devicemap" even that would not do a great harm. Werner On Wed, Jan 7, 2015 at 1:52 PM, Bertrand Delacretaz <[email protected]> wrote: > On Wed, Jan 7, 2015 at 1:47 PM, Werner Keil <[email protected]> wrote: > > ...A good question (Volkan/others do you have ideas where it could help > most?) > > is which of the "tree" structure we'd like to sync with Git?... > > We're not talking about *syncing* to Git - what Volkan's suggesting is > *switching* to Git. > > -Bertrand >
