[news.eclipse.technology.equinox] [p2] Tricks and tips for debugging ins

[Eric Rizzo <eclipse-news@xxxxxxxxxxxx>]

I'm having a struggle getting our features to install into p2-enabled 
(Eclipse 3.4 based) applications (Ganymede packages, Rational tools, 
etc). I keep running into dependency issues, but the output that p2 
gives when it can't install is less than useful.
Are there any tricks or techniques that can help an experienced plugin 
developer figure out why his feature won't install? Anything beyond the 
cryptic "Cannot find match..." and "Unresolved dependency..." messages 
that show up in the error log and the p2 UI...

I have to say, this experience is a major step backwards from what we 
had in the pre-3.4 world; I'm not sure if all the blame lies with p2 or 
if some of it is due to PDE not being quite caught up, but in any case 
it is quite disappointing. I'm not new to Eclipse or plugin development, 
either.

Thanks in advance,
Eric