On 08.05.2012 13:31, Balázs Zsoldos wrote: > thank you for the very fast response. I would like to make things a bit > more clear. I would like to create separate jars that contains only the > relevant packages (e.g. osgi-jdbc.jar, osgi-blueprint.jar, ...)
That's exactly what I want to see too. :) > We have a public maven repository where I would like to upload these jars. > Do you have any restriction or recommendation concerning to the maven > groupId:artifactId:version naming? The best would be > org.osgi:osgi-blueprint:4.2.0 but if you prefer I can think in other > grouId first not to occupy the standard one. A common (but unfortunately not enforced or even standardized) recommendation is to use the fully qualified BSN, i.e. org.osgi:org.osgi.service.xyz:1.0.0 would map to a bundle artifact called org.osgi.service.xyz-1.0.0.jar. That approach worked well for me in the past: the full qualification helps to avoid confusion when two teams create similarly named services. That being said, as long as you drop the artifacts only into your private repo, the effective names should not matter much. -h _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
