Indeed - I thought some plugins from Eclipse itself had dependency information in plugin.xml ... But there are no.
Ok - just OSGi ... Jan >-----Ursprüngliche Nachricht----- >Von: Xavier Hanin [mailto:[EMAIL PROTECTED] >Gesendet: Freitag, 16. März 2007 10:20 >An: [email protected] >Betreff: Re: Google Summer of Code > >On 3/16/07, [EMAIL PROTECTED] ><[EMAIL PROTECTED]> wrote: >> >> >> I am not very deep in writing Eclipse plugins ... >> >> >> >> But additional to an OSGi dependency parser a DP for >Eclipse plugins >> >> could be useful >> >> (parsing the plugin.xml and feature.xml). >> > >> > >> >With recent Eclipse versions, Eclipse iteself being based on >> >OSGi, I don't >> >see how parsing a plugin.xml could provide value for >> >dependencies. Indeed >> >plugin dependencies are located in the MANIFEST and follow the OSGi >> >specification. But maybe I'm missing your point? >> >> >> EclipsePlugIns ARE OSGi bundles, that's right. >> But why there are so many dependency information in the plugin.xml's? > > >As far as I know (but I may be wrong), it's only the case with >old plugins, >or for compatibility with old eclipse versions, in which >plugins were not >OSGi bundles. > >I've made a very simple test: create a new Plugin project in >Eclipse 3.2, >chose the HelloWorld template, and there is no dependency info in the >plugin.xml, everything is in the MANIFEST. > >- Xavier > >Jan >> >
