another option would be to define a special case for directory name "core" that this need not to be part of the artifact name. so that we could have
commons/web/base/core -> commons.web.base commons/web/base/jersey -> commons.web.base.jersey The counterpart could be the convention that the artifact suffix "parent" need not be matched by a folder name which can be handy if for some modules you wan to have parent and reactor in one. Cheers, Reto On Wed, Dec 19, 2012 at 6:12 AM, Rupert Westenthaler < [email protected]> wrote: > On Tue, Dec 18, 2012 at 10:11 PM, Fabian Christ > <[email protected]> wrote: > > I have also seen directories with a dot "." in the name like > "base.jersey". > > I have not see such a use of dots in directory names before and to me > this > > is also a bit confusing. Maybe because of the Java convention using the > dot > > as a package / directory splitter. > > There are some examples where a '.' in the artifact id is mapped to an > '-' in the svn path. In addition typically the {framework-name} is in > front of the {module-role}. > I think the first module using this template was the "opennlp-ner" > EnhancementEngine. > > If we apply this to the /commons/web/base.jersey than the module path > would be renamed to "jersey-base" and also the artifact id and > packages would swap the last two elements. However for me it would be > also fine if we just rename the folder from "base.jersey" to > "base-jersey" > > best > Rupert > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen >
