Hi Ali, On Wed, 2018-11-07 at 06:53 +0300, Ali Parmaksız via osgi-dev wrote: > Hi all, > This is a basic question. But i want to ask you why symbolic name is > needed? > Then i think that it is about bundle installation, bundle:install > command > is sometihng like that: > bundle:install mvn:com.groupID/artifactId/version > When i checked manifest.mf, symbolic name is com.groupID.artifactId > Now this is my question, what is relation between symbolic name and > bundle:insall? If symbolic name is not for this, then for what?
The bundle's symbolic name is used mostly inside an OSGi container to perform various operations. The name + version uniquely identify a bundle inside the container. The fact that the bundle's symbolic name is set to groupId + artifactId is a convention, and other projects could: - set the bundle symbolic name to artifactId ( Apache Felix does so ) - select a completely different artifactId The command you referenced installs a bundle from maven coordinates, but there are other ways to do so, notably: - installing from a local/remote jar file - resolving + installing a bundle using a bundle symbolic name and version, based on an OSGi index So to come back to your question - there relation between the symbolic name and the specific install command you referenced is mostly by convention. Hope this helps, Robert _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
