Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Plugins
  1. OpenProject
  2. Forums
  3. Plugins
  4. Plugins with nested namespaces

Plugins with nested namespaces

Added by Ole Trenner almost 11 years ago

Hi,

we are currently using the openproject-plugins plugin to develop several plugins. As far as we understand plugins follow the naming scheme ‘openproject-plugin_name’ and reside in a module ‘OpenProject::PluginName’. We would like to introduce an intermediary namespace, like so: ‘openproject-ourname-plugin_name’, resulting in a module structure like OpenProject::Ourname::PluginName.

So far we haven’t been able to achieve this. Whenever we put the plugin engine in another namespace we get all sorts of errors.

Is this possible at all? The code of acts_as_op_engine (e.g. https://github.com/opf/openproject-plugins/blob/dev/lib/open_project/plugins/acts_as_op_engine.rb#L52) seems to indicate that the nesting and naming is hardcoded.

Thanks for any suggestions!

Cheers,
Ole.


Loading...