...
| Code Block |
|---|
org = same as in old jar (for example: org.apache.httpcomponents) name = info.novatec.[artifctname].jar version = same version as in Bundle-Version header |
Specifying dependencies
Plugins can specify the dependencies in two ways:
- In the Required Plug-ins list of the MANIFEST.MF where all needed plug-ins are explicitly listed
In the Imported Packages list of the MANIFEST.MF where needed packages are defined, but it is not defined from which plug-in they originate.
Tip Eclipse can generate the list of the imported packages on its own. In the MANIFEST.MF > Dependencies > Automated Management of Dependencies you can add any plug-in and execute add dependencies action with selecting the Import-Package options. The Eclipse will analyse what package is used in our plug-in from the list of 3rd party plau-ins and add the import packages where needed. Please mark all the imported packages as optional.
info.novatec.inspectit.commons and info.novatec.inspectit.commmonscs
These two plug-ins specify the dependencies with the Imported Packages option. This was done because of the OSGi Uses Conflict that occured during the build. More about this problem can be found here: http://blog.springsource.org/2008/11/22/diagnosing-osgi-uses-conflicts/
info.novatec.inspectit.rcp
In the manifest fro the inspectIT project In the manifest for the Commons, CommonsCS and inspectIT projects we list all required plug-ins as a dependency via Required Plug-ins option.
...
All the OSGi based bundles should always be resolved to the osgi configuration. This should not be changed, because platform target we use in development is relying on the /lib/osgi folders of every plug-in project for the needed bundles.
info.novatec.inspectit.commons and info.novatec.inspectit.commmonscs
The ivy files in this two projects need to have duplicated lists of needed libraries, since this projects are used as normal java project in CMR and as plug-in in inspectIT RCP:
...