I asked at equinox-dev and it seems there's no Bundle-BuddyPolicy header in OSGi standard
(my question listed in [1] and).

Moreover there's nothing wrong with Eclipse-BuddyPolicy (except it's Eclipse-specific). It should be deprecated - at least as far as I know.

Whether it's good idea to include this Equinox specific header is different question. My personal state is to include it because

* other OSGi frameworks will ignore this header

* for Equinox OSGi it doesn't mean any significant load

* users wishing to go "buddy classloading policy" way will not have to edit manually unpack JAR, modify MANIFEST.MF headers and pack it as JAR again.

On Tue, Jul 10, 2012 at 2:10 PM, ceki <ceki@qos.ch> wrote:

Hi Gunnar, Ekke,

FYI, since a few days, we started publishing a composite p2 repository
at http://logback.qos.ch/p2/. It contains two child repositories,
called "proper" and "beagle". The "beagle" repo publishes the
logback-beagle plugin which is a console-like view for logging. The
"proper" repository publishes bundles for slf4j-api, logback-core and
logback-classic.

OSGi bundles still need a way to pass logback-classic a configuration
file. Several technical for achieving this are explained by Libor
Jelinek at [1]. I think logback-classic should support Eclipse buddy
policy. Would you have any objections if I added
"Eclipse-BuddyPolicy: registered" to logback-classic.jar's MANIFEST ?

Your comments are most welcome,

[1] http://devblog.virtage.com/2012/07/logback-and-eclipse-attaching-logback-xml/

--
Ceki
http://twitter.com/#!/ceki