On 24 Nov 2010, at 15:12 , Bram de Kruijff wrote: > while moving Cassandra into its own subproject I'm noticing some IIMHO > strange things in our naming conventions documented at > http://www.amdatu.org/confluence/display/Amdatu/Internal+naming+conventions > and how there turn out in the real world > > 1) It is documented that a subproject like "amdatu-cassandra" has > groupId "org.amdatu" and artifactId "org.amdatu.cassandra"
That sounds right and is the same as we do in Felix, where the whole project has a groupId of org.apache.felix and each subproject has an artifactId that is of the form <groupId>.<subprojectname> where subprojectname can be something like configadmin, but if there are multiple artifacts from a single subproject such a subprojectname can also be configadmin.filestore. > 2) Also it is documented that the packagename for a module is equal to > groupId concatenanted with artifactid. As packagenaming is restrictive > in the use of characters like - by implicit definition now the > artifactId is too. This leads to all kinds of awkwardness like That sounds wrong, I would say the package names of a module all start with artifactId only (given the definition above). By the way, artifactId will then also be the symbolic name of the bundle. I think it's worth having bundle names that are unique and defining them like this ensures that. It also links the name of the artifact to the symbolic name and version of that bundle (which also makes sense). Greetings, Marcel
