Re: [pde-dev] Eclipse-ExtensibleAPI existence?

Re: [pde-dev] Eclipse-ExtensibleAPI existence?

From: "Chris Aniszczyk" <caniszczyk@xxxxxxxxx>
Date: Mon, 28 Jul 2008 10:03:36 -0500
Delivered-to: pde-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=Vp+H+jENGL7EfZ8fIqAUnyLmDE5xpYzKan3bYAn0FWiQMo4nSqnO2TPp/NneoHK4db Mw5nxi9coEy2oLtMvUjBid+q3jqLzMBIEGdvAt3gpEb4JHydKqpp9IASc9L23GCKfNoP SrjD7lRVFfE5xeOvuXDyxCflKBzYBglYpQo6U=
List-archive: <https://dev.eclipse.org/mailman/private/pde-dev>
List-help: <mailto:pde-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/pde-dev>, <mailto:pde-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/pde-dev>, <mailto:pde-dev-request@eclipse.org?subject=unsubscribe>

My question is why this limitation exist? Is there particular reason why
fragments are added always to the compile classpath of the clients?

This is to improve the experience during development time.

Tom has a good response here why the header exists:

http://markmail.org/message/erqkynrt5zdlxojv

--
Cheers,

~ Chris Aniszczyk

Follow-Ups:
- Re: [pde-dev] Eclipse-ExtensibleAPI existence?
  - From: Danail Nachev

References:
- [pde-dev] Eclipse-ExtensibleAPI existence?
  - From: Danail Nachev