Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] How to document OSGi extensibility? 
> To be clear, Eclipse Platform is not an incubator of OSGi, it's placed
> downstream of OSGi and leverages what is released.

I think that's not completely true the specification header[1]

Eclipse-BuddyPolicy 		
Eclipse-BundleShape 		
Eclipse-ExtensibleAPI 		
Eclipse-PlatformFilter
Eclipse-RegisterBuddy
are origin of the Eclipse Foundation and are (afaik) more or less of Eclipse Platform usage/requirements. And as platform heavily depends on Equinox I more count that as part of platform as well as being an independent part that is "just" an OSGi implementation.
Anyways no one has asked to have @noextend and a like to be part of another project so it seems not unusual for the platform to define some custom annotations/documentation means.
I'm not against proposing such a thing at OSGi itself, but waiting for it might take some time and its worth to at least show some usage before proposing a change to include it officially. 


[1] https://www.osgi.org/bundle-headers-reference/


Am 22.01.21 um 16:23 schrieb Mickael Istria:
On Fri, Jan 22, 2021 at 4:05 PM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx <mailto:laeubi@xxxxxxxxxxxxxx>> wrote: 

    OSGi already defines some annotations for the package level see , OSGi
    DS makes heavy use with great success of annotations.
OK, can you please share a link to such example of package-info that's the good OSGi way. Maybe we can just mimic that and be done with it. 

    The problem is more that the Eclipse way of thinking is sometimes
    incompatible with standard OSGi ;-)
I think it's more that Eclipse Platform developers are not really top OSGi experts. They're using OSGi here and there as it fits, but Eclipse still has an extension registry and many other things that -despite some technical limitations- do work very well in most cases and that make people still rely on them without having to leverage OSGi much. 
And this Whiteboard annotation isn't standard OSGi (yet?)

    But I think if a draft for a @Whiteboard annotation could be
    provided in
    Eclipse it might become the reference-implementation of an official
    Eclipse specification later on :-)
    [1]
    https://blog.osgi.org/2018/07/osgi-r7-highlights-bundle-annotations.html
    <https://blog.osgi.org/2018/07/osgi-r7-highlights-bundle-annotations.html>
To be clear, Eclipse Platform is not an incubator of OSGi, it's placed downstream of OSGi and leverages what is released. So while Eclipse Platform code can be used as example (in some WIP/Drafts Gerrit patch) to help with design of such annotation for OSGi, the project doesn't aim at being a reference implementation to host such experimentation and won't merge experimental code. That said, Equinox may be interesting in hosting such development. It's more a topic to bring on the equinox-dev@xxxxxxxxxxx <mailto:equinox-dev@xxxxxxxxxxx> mailing-list; which I believe has more interaction with the OSGi Working Group so such development likely to be more successful there. 

_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev

Back to the top