failure to understand a full path when loading a plugin

Bug #290748 reported by Toru Maesaka
4
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Monty Taylor

Bug Description

A plugin is loaded by supplying the library name with the --plugin_load option but it will fail to do so when a full path to the library object is provided. Furthermore, a user cannot tell if a failure had occurred since drizzle will still start without reporting the failure.

Changed in drizzle:
importance: Undecided → Medium
milestone: none → aloha
Revision history for this message
Andrew Ettinger (sillydeveloper) wrote :

I like that it is robust enough to start without reporting the failure, but it should probably warn you fairly loudly that the plugin did not load.

Revision history for this message
Jay Pipes (jaypipes) wrote :

Assigning to Monty. Yeah, this is definitely worthy of attention. Basically, the plugin_load and whole compilation process for plugins needs to be documented at least...there's just not much information (or at least accurate information) on the wiki to make informed decisions.

Changed in drizzle:
assignee: nobody → Monty Taylor (mordred)
status: New → Confirmed
Revision history for this message
Jay Pipes (jaypipes) wrote :

plugin_load, --with-plugins, are all no longer valid now due to the new plugin compilation process and Python plugin script.

Changed in drizzle:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.