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

[Andrew Niefer <aniefer@xxxxxxxxxx>]

In pde.build at least, the fragments
are added to the classpath regardless of the ExtensibleAPI header.

A brief look at the code seems to say
the affect of this header is the order in which jars are added to the classpath.
 The fragment's libraries come before the host when ExtensibleAPI
(or "Eclipse-PatchFragment"
) is specified, otherwise the host comes first.

-Andrew

Danail Nachev <d.nachev@xxxxxxxxxx>
Sent by: pde-dev-bounces@xxxxxxxxxxx

07/28/2008 11:08 AM

Please respond to
"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>

To	"Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-dev] Eclipse-ExtensibleAPI existence?

:) Sorry, a simple "not" makes a lot of
difference.

I meant: Is there particular reason why fragments are *not* always added
to the compile classpath of the clients?

BR,
--
Danail Nachev
Senior Software Engineer/Development Tools
ProSyst Labs EOOD
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------

Chris Aniszczyk wrote:
> 
>     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
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> pde-dev mailing list
> pde-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-dev
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev