[news.eclipse.technology.equinox] Re: How do you handle library classes

["Pascal Rapicault" <pascal_rapicault@xxxxxxxxxx>]

The order in which classes are found is described here:
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home/dynamic
Plugins/currentPluginModel.html

So in this case, the xerces you'll get will depend on the order in which the
A and B appears in the requirements.

There is no ambiguity. If A want xerces from B it just has to change its
requirement order, and if it wants another one, then it just specifies it,
or directly put the jar it needs into itself.

    PaScaL

"Kevin" <supreme_java_guru_1@xxxxxxxxx> wrote in message
news:b7493v$9o0$1@xxxxxxxxxxxxxxxx
> I am curious, if plugin A depends on B that has xerces.jar 1.0 and also
> depends on C that has xerces 2.0, and A uses xerces, first of all which
one
> does A use? Second, is there any issue like runtime ambiguous names or
> something? How does A know to go to B for 1.0 as opposed to C for 2.0 or
> vice versa OR even not use either because they aren't the version A needs?
>
>
>