Skip to content

[Feature Request] Introduction of launcher flag to use symbolic name as location #3810

@amitjoy

Description

@amitjoy

Current State: Launcher uses the bundle path as its location which makes sense to support multiple versiond of bundles having same bundle symbolic name.

Requirement: We might need a flag for launcher to allow using bsn instead of bundle path.

Scenario: Let's say, we have the following bundle in the launcher exported uber JAR.
com.example.bundle.a Version 1.0
Now, once we use the uber JAR, the OSGi storage will have all the bundles expanded in their proper locations - in this scenario, the bundle location of Bundle A will be - jar/com.example.bundle.a-1.0.0.jar
(considering com.example.bundle.a will be consumed from remote maven repo, such as, maven central). Now, if we update the bundle in uber JAR to use 2.0.0, the storage will now contain Bundle A in two different locations - jar/com.example.bundle.a-1.0.0.jar and jar/com.example.bundle.a-2.0.0.jar.

Hence, we might need a flag for launcher that enables us to use bsn instead of path.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions