I guess this should work this way:
1. StandardScriptBuilder, which is also a build participant runs first (always), and builds model elements for every build path entry (verify that your library is a part of the buildpath)
2. Your build participant runs after model for all build path entries is built, so you are able to "see" all PHP elements of a project & its dependencies.
On Sun, Jun 21, 2009 at 12:28 PM, Robert Gruendler <doobre@xxxxxxxxx
right now i just added it manually by adding it in the preferences
as "User defined Library", then in the
properties of the project: PHP Include Path -> Libraries -> Add
Michael Spector schrieb:
How do you define your included library? We don't encounter
this issue in our build participant.
On Sat, Jun 20, 2009 at 10:30 PM, Robert Gruendler
i'm trying to understand how included libraries are handled
model point of view in pdt.
Basically, we need some information from specific classes
the user library, but i'm not sure at
which point we can hook into pdt to build our model. I've
add a buildparticipant extension which
uses a class that extends PHPAstVisitor.
This works fine for all classes/methods etc inside the project,
but i don't get anything from the included library.
I assume the php model for the external libraries does not get
built during the regular build process.
Could anyone give me a hint at which point of the pdt plugin
lifecycle the external libraries get parsed to build
the model for them ?
pdt-dev mailing list