Plug-in JAR paths should support paths relative to the plugins.dir setting in base.config

[Nicklas Nordborg]

If the start of the plug-in JAR path matches the plugins.dir setting we replace that with %plugins.dir%, for example:

  /usr/local/base/plugins/illumina-plugins.jar

is stored as

%plugins.dir%/illumina-plugins.jar

in the database. The conversion should be automatic in the core and only the real path should be shown to users. Other benefits:

• Running on a job agent were the root path is different means that we only have to change the setting in the base.config file.
• Moving the plug-ins to another directory also means that we only have to change the setting

in base.config

This scheme should also be followed by other places were a JAR path is needed. See for example #911.

[Nicklas Nordborg]

(In [4113]) Fixes #913: Plug-in JAR paths should support paths relative to the plugins.dir setting in base.config

[Nicklas Nordborg]

(In [4114]) References #913: Added some documentation

[Nicklas Nordborg]

Reopens this ticket because I think the implementation is not Windows-friendly.

[Nicklas Nordborg]

(In [4122]) References #913: Plug-in JAR paths should support paths relative to the plugins.dir setting in base.config

The windows problem should now be solved, but need to test it also.

[Nicklas Nordborg]

Now tested on windows.