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

["Peter Kahn" <citizenkahn@xxxxxxxxx>]

Thanks.  excellent suggestion.  I have done this.  I have created a
feature and two plugins.  The feature depends on both and plugin a
depends on plugin b.  Everything works and this is great.

Now, I need to figure out why my actual build isn't working.

So, what does the pde build system use to locate a plugin within the
plugin directories?
    Is the MANIFEST.MF what is used to search for the plugin?
    does the directory name under plugins matter  (
${buildDirectory}/plugins/org.myproj.a vs
${buildDirectory}/plugins/anything-i-want )
    does the map file play a role after the fetch is done?

Basically, I'd like to know which files are involved in the finding of
the plugin.

Thanks again.


On 7/29/07, Barrie Treloar <baerrach@xxxxxxxxx> wrote:
> On 7/29/07, Peter Kahn <citizenkahn@xxxxxxxxx> wrote:
> > Thanks.  That is how I'm set up...sort of..
> > buildDirectory is pointing to root and baseLocation was pointing to a
> > copy of eclipse.
>
> This sounds fine.
>
> > 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?
>
> I'm saying that when you are building a plugin your dependencies can either be
> a) in the baseLocation (already built and ready to go)
> b) in your buildDirectory/plugins (which should be automatically built
> as part of the PDE process)
>
> > 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)
>
> baseLocation = eclipse install
> buildDirectory = ROOT.
>
> If they are both set to ROOT it will not work.
>
> > 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?
>
> I think so.
>
>
> I recommend trying to sort out your automated build on a very simple
> test project first.
> Try using one of the template plugins that Eclipse can generate for
> you, like the HelloWorld.  Get that working and the slowly extend it
> to depend on other plugins in ways similar to your project and get
> those working too.
>
> You will then be able to spot what is wrong with your project and fix it.
> _______________________________________________
> pde-build-dev mailing list
> pde-build-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-build-dev
>


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