On 9 Mar 2013, at 11:10, Christian Grobmeier wrote: > On Fri, Mar 8, 2013 at 10:04 PM, Jordan Zimmerman > <jzimmer...@netflix.com> wrote: >> Out of curiosity, why do the Onami artifacts have org.apache.onami in them? >> Typically this is only in the groupId. > > No reference at the moment, but if you search the mailinglists: > http://mail-archives.apache.org/mod_mbox/incubator-onami-dev/ > > Simone explained somewhere its necessary for some OSGi magic.
FYI, OSGi doesn't mind what Maven artifactId you use, since it works off the OSGi metadata in the manifest. Each bundle should be uniquely identified by the Bundle-SymbolicName and Bundle-Version. The bundleplugin defaults set the Bundle-SymbolicName to be "groupId.artifactId" with any common segments collapsed. So from both OSGi and the bundleplugin's perspective it's not necessary to have org.apache.onami in the artifactId. Some projects choose to have their artifactIds prefixed with their namespace, but AFAIK this is more so that people downloading jars directly from the Maven repository get the full name rather than just the short form (since the default Maven repository layout is "groupId/artifactId/version/artifactId-version.type"). Some deployment tools/scripts might also prefer the artifactId to be fully qualified like the Bundle-SymbolicName, to make it easier to map between Maven and OSGi coordinates - but that would be a feature of the tool rather than a limitation in OSGi. HTH > Maybe its a good thing to document as it the question comes up from time to > time. > > Cheers > >> -Jordan > > -- > http://www.grobmeier.de > https://www.timeandbill.de
