A basic OSGi manifest will make jsyntaxpane behave as a drop-in component
for an OSGi environment with no impact on other usage.
The easiest method of achieving this is to integrate the "bnd" tool
(http://www.aqute.biz/Code/Bnd) into your build process. Be sure that ALL
of the imports are optional and that all internal packages are exported.
Additionally include a meaningful symbolic id, name, and version
I've used the "wrap" tool (ant/maven task, cli) within bnd to create a
plugin with the following properties file
-nouses:true
Bundle-Version: 0.9.5.b29
Bundle-Name: JSyntaxPane
Bundle-SymbolicName: jsyntaxpane
Import-Package: !jsyntaxpane, *;resolution:=optional
Original issue reported on code.google.com by c.ca...@gmail.com on 12 Nov 2009 at 2:52
Original issue reported on code.google.com by
c.ca...@gmail.comon 12 Nov 2009 at 2:52