Enrique This does make sense. At this point we have not called out OSGi specific/particular things in the doc. We have looked at providing a "pure OSGi mode" in the tooling but in the end that amounted to turning off the Extensions and Extension Points tabs and filtering a few of the options in the wizards (e.g., trimming the Templates). For example, if you don't create Extensions or Extension points then the plugin.xml is not created. Things like Fragments are part of OSGi R4. In general, if you look at a manifest.mf and see "Eclipse" in the headers or "x-" in the attributes/directives then it is extra. If not, it is standard. Other than that, Eclipse plugins are OSGi bundles.
WRT using things like SWT etc, those are just bundles. Dependencies on these are not added unless you need/want them (e.g., if you pick a template that has UI). Coding against these bundle is the same as coding against any bundle. There are dependencies to be met and API to be used if needed. This point is more one of having a rich set of bundles available and needed to sort out what is what. The summary is that we can (and will) do better in the tooling but the present tooling addresses the very significant issues of classpath management and incremental building/launching/testing. In our experience, those are the places that developers really get tripped up and spend time. Jeff Enrique Rodriguez <[EMAIL PROTECTED]> 08/23/2005 10:33 AM Please respond to oscar-dev To oscar-dev@incubator.apache.org cc Subject Re: Tooling On 8/23/05, Jeff McAffer <[EMAIL PROTECTED]> wrote: > I noticed some posts here on tooling to support bundle development. I > thought I would take the opportunity to point out that Eclipse has a > comprehensive suite of support for bundle development in the form of a > Plugin Development Environment (PDE)... Hi, Jeff, Is there by any chance a tutorial (with pictures) on using Eclipse for straight-up OSGi bundle development? Something that expands on the plugin --> bundle mapping? Something for total beginners to both Eclipse and OSGi? In particular, something targeted to those of us wishing to create OSGi bundles for server-side components that won't be using any Eclipse UI/SWT, etc.? The 3.1 PDE Guide and the PDE screens don't make it clear what's OSGi and what's Eclipse, eg plugin.xml, Fragments, and Extension Points. I have an idea of what's OSGi and what's Eclipse, but I don't think most people do, and the mental mapping of plugin --> bundle breaks down at some point. I'd like to make sure I'm not relying on or generating anything that is not "pure" OSGi, since I'm working on purely server-side bundles and I'm sure that other developers at Apache have the fear that the IDE is automatically generating unnecessary artifacts behind the scenes. Perhaps a mode is in order for pure bundle development, with pure OSGi semantics. Does that make sense? Enrique
