Fuse ESB: setting package version with wrap url on non OSGi jar

Solution Verified - Updated -

Environment

  • Fuse ESB 7.1

Issue

  • How to set the bundle version information when using the "osgi:install wrap:mvn..."

Resolution

installing within the karaf console using osgi:install and wrap url setting the

  • Bundle-SymbolicName
  • Bundle-Version
  • Export-Package with version numbers

osgi:install -s 'wrap:mvn:com.example.myjar/myjar/1.0.3$Bundle-SymbolicName=myjar&Bundle-Version=1.0.3&Export-Package=com.example.myjar;version=1.0.3,com.example.demo;version=1.0.3'

NOTE: the single quotes above are important

and in a features file :

...

<feature name="myfeature">
 <bundle>wrap:mvn:com.example.myjar/myjar/1.0.3$Bundle-SymbolicName=myjar&amp;Bundle-Version=1.0.3&amp;Export-Package=com.example.myjar;version=1.0.3,com.example.demo;version=1.0.3</bundle>


...

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

1 Comments

The wrapping of a jar file automatically generates bundle imports and exports. Can I append packages to the auto-generated exports and/or imports using this annotation or will the example above just overwrite the auto-generated imports/exports?