[osmosis-dev] API 0.6 and unique keys

[marcus.wolschon at googlemail.com]

On Tue, 03 Feb 2009 22:41:21 +1100, Brett Henderson <brett at bretth.com>
wrote:
> I hope I didn't come across critical, it wasn't my intent.  This one is 
> almost impossible to diagnose without being able to reproduce it so 
> you've done all you can.  In fact I wasn't suggesting there was a bug in 
> the JPF support either, just that the current error (or lack thereof) 
> makes it hard to diagnose.
> 
> What I'm wondering is whether it is possible to register each plugin 
> individually and log a fine/finer message stating the plugin file name 
> before we do it.  It would mean that if an error does occur we can at 
> least identify exactly which plugin caused the failure.  Currently the 
> code contains this statement in the registerJpfPlugins method which is 
> the one that failed:
> pluginManager.publishPlugins(locations.toArray(new 
> PluginLocation[locations.size()]));
> 
> That statement is publishing all located plugins in a single call to JPF 
> which means that in cases like these it can be difficult to pinpoint the 
> problem.
> 
> Is it possible to publish each plugin individually?  Perhaps that makes 
> no sense ... I really need to get familiar with JPF :-)


Hello Brett,

I guess that's not problem.
Just change it as you just said and try if test.bat still works.

Marcus