Skip to content

Automatically detect which dependencies should be added as libraries #568

@Riduidel

Description

@Riduidel

According to wisdom documentation, using non-OSGi dependencies requires adding them as libraries to the generated bundle.
Unfortunatly, we don't know beforehand if a dependency is a valid OSGi bundle or not.
However, there are methods to detect such bundles. Typically, this StackOverflow answer provides a first-level solution.
Could it be possible to detect which dependencies are valid as OSGi, and which are not, in order to automate the tag generation ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions