[pde-build-dev] RE Missing required plugin-in....

["Peter Kahn" <citizenkahn@xxxxxxxxx>]

Thanks.  That is how I'm set up...sort of..
buildDirectory is pointing to root and baseLocation was pointing to a
copy of eclipse.
So, if plugin A relies on 3rd party plugins from eclipse and my own
plugins (plugin B) then are you saying that I must set the
buildDirectory and baseLocation to the ROOT and copy in the 3rd party
plugins?

If baseLocation is set to eclipse and buildDirectory is set to root or
if they are both set to root I get the same error (although I do get
more warning in the second case since the 3rd party plugins cannot be
found)

When it tries to generate the scripts, the genericTarget fails to
locate one of my plugins.

It should be looking in ROOT/plugins/${id}  for this plugin right?


On 7/28/07, Peter Kahn <citizenkahn@xxxxxxxxx> wrote:
> Can someone help me with a headless build plug-in question...
>
> How does the system determine the location of a dependency for a
> plugin when building a feature?

either your plugins/features are built as part of your project, in
which case they are
ROOT/
 - plugins
   |-- plugin A
   |-- plugin B
 - features
   |-- feature A

Or the plugins are in your eclipse target platform, defined in your
build configuration build.properties file
(http://help.eclipse.org/help32/topic/org.eclipse.pde.doc.user/guide/tasks/pde_product_build.htm)
setting "baseLocation".

You can also do something with specifying another relative directory
to locate plugins, but I have never used it.

-- 
Peter Kahn
citizenkahn@xxxxxxxxx
citizenkahn@xxxxxxxxxxxx, pkahnpie1@AIM
http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/
Awareness - Intention - Action