Bug #1640
Loading same plugin twice from different pathes
| Status: | Closed | Start date: | 10/01/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | J. Wienke | % Done: | 0% | |
| Category: | Configuration | |||
| Target version: | Robotics Service Bus - rsb-0.11 |
Description
If two or more (2+) plugin paths are configured, and a specific plugin is available in 2+ of these plugins paths, rsc tries to load this plugin 2+ times, resulting in duplicate entries.
Instead rsc should just load the first occurrence of a plugin (in the order given by the plugin path configuration).
Related issues
History
#1 Updated by Anonymous over 10 years ago
- Priority changed from Normal to High
#2 Updated by J. Wienke over 10 years ago
I just looked at the code and there is a unit tests that actually tests that one path overrides another one: PluginTest::testPathOverriding. There would be an exception if the plugin was loaded twice. Could you please explain in more detail what happens in your case?
#3 Updated by Anonymous over 10 years ago
- Assignee set to J. Wienke
It seems, that you already adressed this issue in a3932651bd, but did not close it. ;)
#4 Updated by J. Wienke over 10 years ago
But then the description is actually wrong. ;) That commit addressed the issue that the configuration requested to load the same plugin twice, and not that two version of the plugin in different folders existed.
#5 Updated by Anonymous over 10 years ago
- Status changed from New to Feedback
Daniel, I remember, that this issue came up in a setup of yours, where you had the toolkit plugin path configured and a local plugin path with a locally built plugin.
Any chance, that you could reproduce the issue you had back then? Otherwise I would consider this issue resolved.
#6 Updated by J. Wienke over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
As we did not get any feedback before the new release date we move this issue over to the new version.
#7 Updated by J. Wienke over 10 years ago
- Status changed from Feedback to Closed
Please reopen if still valid