Forrest
  1. Forrest
  2. FOR-741

Enable dynamic loading of plugins

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.7, 0.8
    • Fix Version/s: None
    • Labels:
      None

      Description

      Create a new plugin resolving mechanism that loads plugins at runtime rather than at startup. We need to modify the Locationmap somthing like this:

      <match pattern="plugin.xmap.*">
        <location src="{project:tmp}/{1}/>
        <install src="http://f.a.o/plugins/0.8/{1}/>
        <install src="http://f.a.o/plugins/0.7/{1}/>
        <location src="{forrest:plugin.fallback}/error.pluginNotFound.xmap"/>
      </match>

      The we can dynamically install features at run time rather than at startup. We would even be able to add plugins at runtime.

        Issue Links

          Activity

          Hide
          Ross Gardler added a comment -
          Currently plugins are used from the build directory, if we do a Forrest clean it removes the plugins thus causing someone to have to download again, this would not be necessary if the plugins were used inplace and the src was available.
          Show
          Ross Gardler added a comment - Currently plugins are used from the build directory, if we do a Forrest clean it removes the plugins thus causing someone to have to download again, this would not be necessary if the plugins were used inplace and the src was available.
          Hide
          Ross Gardler added a comment -
          Currently plugins are used from the build directory, if we do a Forrest clean it removes the plugins thus causing someone to have to download again, this would not be necessary if the location of the plugin install was somewhere other than the the forrest build directory
          Show
          Ross Gardler added a comment - Currently plugins are used from the build directory, if we do a Forrest clean it removes the plugins thus causing someone to have to download again, this would not be necessary if the location of the plugin install was somewhere other than the the forrest build directory

            People

            • Assignee:
              Unassigned
              Reporter:
              Ross Gardler
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development