Plugin project - Dependencies page (II)
27 January 2008This post is in continuation of Plugin project - Dependencies page (I). Do read that before this one.
If your plug-in requires a specific version of a plug-in to function properly, then you can specify the version required along with the version match rule. You can read more about valid values in the Platform ISV guide.
The Eclipse runtime gives the flexibility to declare a dependency on a package without explicitly identifying its originating plug-in. These packages are listed in the Imported Packages section.
The Dependency Analysis contain several useful features such as finding cycles in the dependency graph. Such cycles are forbidden by the runtime, making the analysis useful for performing a sanity check on your plug-in’s dependency graph before testing it.
For a selected plug-in in the list, Compute Dependency Extent will give you a list of all the Java types and all the extension points that your plug-in needs from that dependency. So, in essence, it tells you why you need that plug-in.
Since the JARs from all the plug-ins in the list of dependencies will be on your plug-in’s classpath at runtime, it is very important to not have any dependencies that you do not need, as they would slow down classloading. To find such extraneous entries and remove them, use the Find Unused Dependencies feature available on this page.
Related Posts:
- Plugin project - Dependencies page (I)
- Plugin project - Overview page
- Eclipse Plug-in Development Environment (I)
- M2Eclipse (Tycho)
- Plugin project - Build configuration page
- Eclipse Plugin Project - Source pages (I)
- Plug-in manifest editor
- Creating a plug-in project (I)
- Setup a Struts 2 application
- Creating a Simple Plug-in using PDE (I)
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: Plugin project - Dependencies page (II)
