I\'ve got a question on Maven naming conventions (groupId, artifactId and directory names) in a multiple module project with a hierarchical directory structrure.
Another possible approach is to look at function groups more than hierarchy.
Say project B has webapps, plugins and core librairies, then all modules share the same group id (com.mycompany.b) and artefacts are respectively named webapp-???, plugin-??? and core-???.
We also use the -parent convention mentioned earlier: therefore, the parent POM for all webapps is called webapp-parent.pom.