[pde-dev] PDEState and state caching

[Philippe Ombredanne <pombredanne@xxxxxxxxx>]

Hi:
I have a question on PDESate
I am building a set of ant tasks that re-use PDEState to validate the
state of an arbitrary set of bundles and plugins, all external.

I get a PDESate to obtain a State with :
PDEState pdeState = new PDEState(new URL[0], urls, true, new
NullProgressMonitor());
State osgiState = pdeState.getState();
IPluginModelBase[] targetModels = pdeState.getTargetModels();

and then I iterate over that to get errors:
BundleDescription bd = targetModels[i].getBundleDescription();
ResolverError[] re = osgiState.getResolverErrors(bd);
and do some simple analysis of that.

It works great but the second time I run it on a set of bundles that
cannot be resolved, its runs without detecting errors.
It sounds that PDEState does some smart caching...based on time stamps
How to disable that?
Is that with System.setProperty("pde.nocache","true") ? But it seems to
apply only to 'workspace' plugins, while I am feeding only target
stuffs.
I tried to create the PDEstate with resolve true or false. no changes.
Or some other trick?
Would just cleaning the directory be enough?

I would like to avoid hacking the PDESate code, which is so cooool!
Cordially

-- 
Cheers
Philippe

philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com 
nexB - Open by Design (tm) - http://www.nexb.com 
http://easyeclipse.org  -  irc://irc.freenode.net/easyeclipse