Switch to the MANIFEST.MF (or the “Dependencies” tab) to check that the Import statement has been added. Use the same “magic” to add an import for BundleContext and the errors are gone. Move the cursor over the unknown BundleActivator and you’ll see this popup:Īdding an OSGi framework sounds like a very good idea, and if you choose this option, you find that Eclipse also adds an import statement for BundleActivator. Remove the import statements at the top of Activator.java.
Copy the package with our two classes into the src folder of the new plugin project. Maybe the single most interesting feature about that sophisticated manifest editor is its support for managing dependencies. Try to change the bundle name to “HelloWorld” again using either approach.
As is common with such views in Eclipse, you’re free to enter information using the forms or edit the source directly. The tabs “Overview”, “Dependencies”, “Runtime” and “Build” are essentially sophisticated forms for editing the information maintained in MANIFEST.MF (and build.properties). PDE provides a “graphical view” on the bundle configuration (the textual view is still there if you want to see it, click on the last but one tab at the bottom of the window). The build.properties basically adds some information about the project layout and what to put additionally into the created jar (no need to use the export jar wizard any more).ĭouble click on MANIFEST.MF. This sounds familiar, it’s exactly what we have done in our previous, completely “manual” approach. The MANIFEST.MF is here because PDE maintains almost the complete data required to build the bundle in that file. The wizard has created a MANIFEST.MF and a file build.properties. Looking at the resulting project, you’ll find that it isn’t completely empty after all. On the first page, make sure to choose a standard OSGi framework as target:Īnd on the last page uncheck the template option – we want an empty project. You have to change two options while going through the dialogue. I used SimpleBundle-plugin as project name, because this is just a different way to build our Simple Bundle. If it is not already included in your Eclipse installation, get it now 1.Ĭreate a new plug-in project using the wizard. Since then, Eclipse has provided the Plug-in Development Environment (PDE) which is essentially a development environment for OSGi plug-ins. You may have heard about OSGi for the first time – just like I did – when the Eclipse developers announced in 2003 that they’d use OSGi as foundation for the next Eclipse version. Surely, an IDE should provide some support for this. The dependency on the BundleActivator in our Simple Bundle provided a first taste: because of using that OSGi interface, we had to add a jar to the project and an import statement to the project’s manifest. It is a graphical replacment for Eclipse resource history.While the basic mechanisms of OSGi are quite simple, managing an OSGi project can easily get complicated. Subsequently, one may also ask, what is Eclipse CVS?Įclipse Version Tree Plugin is an easy to use, graphical version tree for project artifacts hosted in a CVS repository. Eclipse will detect that the folder is already shared and resolve the connection with CVS. Just right-click on your project and click Team -> Share Project. Enter the required information, and click OK.Īlso, how do I import a project from CVS to eclipse? 2 Answers. In Eclipse, open the Repositories view, right-click that view, and select New→ Repository Location, opening the Add CVS Repository dialog. Just so, how do I connect my eclipse to CVS?