You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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 ?
The text was updated successfully, but these errors were encountered: