Re: [pde-build-dev] unable to find plugin

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

I believe that when you setup the build.properties
and indicate the location of the base Eclipse, that base can have a standard
links directory that can point to various extension locations and thus
other plugins.

Jeff

Allen Lee <alllee@xxxxxxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

11/03/2005 03:17 AM

Please respond to
"Eclipse PDE Build developers list."

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	Re: [pde-build-dev] unable to find plugin

Thanks for the prompt and helpful response!  It
is in fact an unresolved
dependency on GEF.  

Is there a way to specify additional places to look for pre-built plugins
to
compile against besides the baseLocation property?  We are maintaining
the GEF
plugin locally as an extension location instead of with the system-wide
Eclipse install so when PDE checks the baseLocation it won't find the
pre-built GEF plugin there. None of the environment variables listed in
the
automation article or the seem to address this issue.  I tried adding
GEF to the .map
file so that it would be downloaded along with the rest of the plugins
but
that didn't help (in hindsight I suppose that makes sense.. though maybe
that's just because it's getting late).  Perhaps there's a way to
tell the
build process to compile the downloaded GEF plugin first and then somehow
use
that to compile against?  Hmm.. probably the simplest thing would
be just to
punt it to the sysadmins and have them place the GEF plugin along with
the
rest of the system-wide Eclipse plugins.

Thanks again for all your help! 
Allen

On Wed, Nov 02, 2005 at 09:55:30PM -0800, David Olsen wrote:
> Allen Lee wrote on 11/02/2005 21:31:56:
> 
> > The plugins are successfully retrieved from CVS but shortly thereafter
> the
> > process bombs out with a CoreException and an error message 'Unable
to 
> find
> > plugin: XXX_0.0.0'. 
> ...
> > The response from Vasant seems to indicate that it could be a
> > missing dependency which I am worried may be the case; our plugins
have 
> a
> > dependency on GEF 3.1 that I'm not sure how best to satisfy in
the 
> automated
> > build process; GEF is not installed in the standard eclipse plugins
> location
> > but in an extension location instead.
> 
> In my experience, a missing plugin dependency is the usual cause of
the 
> 'Unable to find plugin' message.  Look at your <workspace>/.metedata/.log
> file.  If there are missing dependencies, they will be listed
there.
> 
> (The .metadata/.log file often has useful information that is not
in the 
> build log, so that is always the first place I look when a build fails.)
> 
> --
> David Olsen
> IBM Rational
> Beaverton, Oregon
> _______________________________________________
> pde-build-dev mailing list
> pde-build-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev