Hey Paul,
Its really up to a project and convention you take, enroute asumes org +
artifact but nothing prevents you from doing opposite.
A common pattern I used for maven based projects is:
symbolic name: ${groupId}.${artifactId}
export package: !${groupId}.${artifactId}.internal.*,
${groupId}.${artifactId}.*
bundle name: ${project.name}
This allows to use compact artifact names while keeping some order of
things. When navigating over repository contents you can always be
certain that package org.code_house.foo.bar comes from
org.code_house.foo group and bar artifact.
This, however differs from time to time and different projects take
their own path. For example karaf uses quite long and redundant artifact
names which overlap with module root package. It works quite well there.
Each of above approaches have it pros and cons.
Cheers,
Łukasz
On 15.06.2018 02:40, Paul F Fraser via osgi-dev wrote:
> When creating new maven modules the default module package is set as
>
> org. + the artifactId
>
> Could this be changed to use
>
> groupId + artifactId instead?
>
> Or is there a reason for not doing this?
>
> Paul Fraser
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
