#364 closed enhancement (fixed)
Support for automatic install of non-core plugins
Reported by: | Jari Häkkinen | Owned by: | Martin Svensson |
---|---|---|---|
Priority: | major | Milestone: | BASE 2.5 |
Component: | core | Version: | |
Keywords: | Cc: |
Description
It would be nice to get an automatic install/update of non-core plugins from an official site like http://baseplugins.thep.lu.se. Somekind of user interface is needed and then also support in the core to perform the steps usually done during installation/upgrade of a plug-in.
Change History (19)
comment:1 Changed 16 years ago by
Type: | defect → enhancement |
---|
comment:2 Changed 16 years ago by
Milestone: | BASE 2.x+ → BASE 2.5 |
---|
comment:3 Changed 16 years ago by
Owner: | changed from Nicklas Nordborg to Martin Svensson |
---|---|
Status: | new → assigned |
comment:4 Changed 16 years ago by
comment:5 Changed 16 years ago by
comment:6 Changed 16 years ago by
(In [3704]) References #364 Moved the PluginInfo? class to another package, added a class to handle information about configurations for each plugin info object. And some smaller adjustments.
comment:7 Changed 16 years ago by
comment:8 Changed 16 years ago by
comment:9 Changed 16 years ago by
comment:11 Changed 16 years ago by
(In [3733]) References #364 The functionallity is more or less done. The internal class in PluginInfo? to read jars needs to be refactored and moved to class JarClassLoader?, also some testing and documentation before this can be closed.
comment:15 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [3760]) Fixes #364, Uses the existing JarClassLoader?, when reading/loading jar-files instead of an internal class
comment:16 Changed 16 years ago by
comment:17 Changed 16 years ago by
comment:18 Changed 16 years ago by
- Test program now looks for the test plug-ins: JarPlugin? and NullPlugin?
- Changed FileUtil?.findFiles to use a regular expression filter instead
- Example plug-ins are included in 'ant dist'
A first step in this direction would be to make it easier to register plug-ins with BASE once they are installed on the server. For example, in base.config we add a 'plugin.dir' setting which points to a directory where all plug-ins MUST be installed. BASE can then scan this directory for JAR files containing plug-ins. To know which JAR file that does have plug-ins we need to make the plug-in developers include a file with information about this. In the simplest form it would just list the class names of the plug-in classes. For future enhancements it is probably a good idea to make this XML based. It could for example also include information about en URL to download upgrades of the plug-in.
After scanning the directory BASE displays a list with new plug-ins and the admin can select those that should be installed.