Allow plugin loading to fail

[amccaskey]

I think we should allow plugins to fail and if they do just throw a warning and continue loading the rest of the plugins. No reason that a plugin failing to load should mean you can't use the framework at all.

[anushkrishnav]

I would like to work on the issue
Can you share more info

[1tnguyen]

I think this is referring to the initialize method in this ServiceRegistry implementation.
Basically, we need to make the "Load plugins" loop handle the loading of plugin share libraries a bit more graciously (e.g., via try-catch, etc.) since some plugins are not mandatory and warnings are sufficient.

[anushkrishnav]

Please assign me the issue , i will start working on it

[1tnguyen]

@amccaskey Have you done any work on this one? @anushkrishnav wants to work on it :)

[amccaskey]

Nope. Please go ahead.

[anushkrishnav]

Awesome will start right away !!

[anushkrishnav]

A simple try-catch should be enough

try{
            context.InstallBundles(path + "/" + std::string(ent2->d_name));
            } catch (std::exception& e) {
              XACCLogger::instance()->error("Error installing bundle: " + path + "/" + std::string(ent2->d_name));
            }

or is something more expected? a task list would be really helpful