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
Is your feature request related to a problem? Please describe.
We have a profile for "fat" OSGi bundles which we seem to have used at some point to package up annotators including their dependencies (in the sandbox). We also have "fat" bundles that we provide as part of the Eclipse plugins.
What we do not seem to have is a nice profile for "lean" bundles that are basically just the JARs of the Maven modules that we have.
Describe the solution you'd like
A suitable profile for adding OSGi metadata at the module level, i.e. to uimaj-core, uimaj-cpe, etc. etc. We might run into trouble because of some split packages, but let's see that when we hit it.
Describe alternatives you've considered
Work with the "fat" runtime bundles.
- Added profile based on the Maven Bundle Plugin
- Profile stages META-INF and OSGI-INF in places where Eclipse PDE expects them so Eclipse would recognize them as bundles
- These locations are also cleaned up on a "clean"
Is your feature request related to a problem? Please describe.
We have a profile for "fat" OSGi bundles which we seem to have used at some point to package up annotators including their dependencies (in the sandbox). We also have "fat" bundles that we provide as part of the Eclipse plugins.
What we do not seem to have is a nice profile for "lean" bundles that are basically just the JARs of the Maven modules that we have.
Describe the solution you'd like
A suitable profile for adding OSGi metadata at the module level, i.e. to
uimaj-core
,uimaj-cpe
, etc. etc. We might run into trouble because of some split packages, but let's see that when we hit it.Describe alternatives you've considered
Work with the "fat" runtime bundles.
Additional context
META-INF
andOSGI-INF
in the places where Eclipse PDE expects themmvn clean
The text was updated successfully, but these errors were encountered: