Re: [eclipse-dev] Plugin Manifest and API Rules

[Mazen Faraj <mfaraj@xxxxxxxxxx>]

thread is already being discussed:  
        https://bugs.eclipse.org/bugs/show_bug.cgi?id=76767#c8
 

Mazen.

"Gunnar Wagenknecht" <g.wagenknecht@xxxxxxxxxxxxxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx

04/07/2005 03:07 PM

Please respond to
"General development mailing list of the Eclipse project."

To	eclipse-dev@xxxxxxxxxxx
cc
Subject	[eclipse-dev] Plugin Manifest and API Rules

Why can't we turn this upside down?

By default, Eclipse should encourage everybody to follow the API rules.
If, however, someone decides "I don't care about, let me import the
internal packages from plug-in X" then Eclipse should honor his decision.
That would solve all problems.

I don't know the OSGi spec and the limitations but I think it's always
a
better solution to adapt to clients and client process instead of forcing
clients into your world.

So, every SDK plugin exports only its API. Plugins, which know they are
using non-API from plugin ABC, can state this in their manifest and the
runtime will give it to them.

Cu, Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev