1) Start the New Project Wizard
2) Plug-in Project
OSGi (from Rich Client Tutorial - Part 1) Eclipse 3.0 introduced a new run-time system based on OSGi standards that uses bundles and a new manifest file (MANIFEST.MF) to implement plug-ins. The use of MANIFEST.MF, in normal circumstances, is completely optional. You will notice that almost all of the 3.0 SDK plug-ins do NOT have one yet all are marked as 3.0 and many do not require the compatibility layer. The only reason you would want to have a MANIFEST.MF is if you need to use a particular OSGi capability that is not exposed through plugin.xml (for example, import-package). Otherwise it's recommended at this time that you don't have one. 3) Plug-In Content
Plug-in Class (from Rich Client Tutorial - Part 1) The generated plug-in class that you may be familiar with in previous releases is no longer required in Eclipse 3.0. You can still have one to hold global data if you like. In this case we would like to hold some global data, rather than use a singleton. This allows us to cleanup after the 4) Templates(Only available when making a UI Plug-in Class)
5) Template Selection(Only available when using "Custom plug-in wizard") 5) Template Selection
![]() ![]() ![]() ![]() ![]() |
(c) Copyright (c) 2004,2005 Refractions Research Inc. and others. |