summaryrefslogtreecommitdiffstats
path: root/pf4j
Commit message (Collapse)AuthorAgeFilesLines
...
* Add Plugin status providerMário Franco2015-05-272-10/+67
|
* specify that PluginClassLoader is a Parent Last ClassLoader - it loads the ↵Decebal Suiu2014-09-051-0/+2
| | | | classes from the plugin's jars before delegating to the parent class loader
* defense for #21Decebal Suiu2014-08-241-3/+7
|
* try to improve logging for DefaultExtensionFinderDecebal Suiu2014-08-071-3/+5
|
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2014-07-301-2/+2
|
* [maven-release-plugin] prepare release release-0.9.0release-0.9.0Decebal Suiu2014-07-301-2/+2
|
* try to resolve issue #20Decebal Suiu2014-07-159-96/+278
|
* load extensions from classpath; before this commit only plugins can declare ↵Decebal Suiu2014-06-112-30/+98
| | | | extensions
* fix an issue that occurs when the plugin developer put the pf4j jar in the ↵Decebal Suiu2014-06-021-9/+9
| | | | plugin's lib folder (or not declare the pf4j dependency with scope provided in pom.xml)
* minor changeDecebal Suiu2014-06-021-1/+1
|
* add info message about pf4j version and the runtime modeDecebal Suiu2014-04-231-3/+2
|
* add version in DefaultPluginManagerDecebal Suiu2014-04-231-0/+14
|
* add dispose method in PluginClassLoaderDecebal Suiu2014-04-232-5/+23
|
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2014-04-151-2/+2
|
* [maven-release-plugin] prepare release release-0.8.0release-0.8.0Decebal Suiu2014-04-151-2/+2
|
* update slf4j to 1.7.5Decebal Suiu2014-04-142-14/+13
|
* rename PluginVersion to VersionDecebal Suiu2014-04-147-55/+54
|
* Move requires logic to isPluginValid(PluginWrapper), rename default version ↵James Moger2014-04-143-26/+35
| | | | to ZERO
* Add an optional requires manifest valueJames Moger2014-04-125-5/+87
| | | | | | | | | | | | | | As integrators of pf4j evovle their extension APIs it will become a requirement to specify a minimum system version for loading plugins. Loading & starting a newer plugin on an older system could result in runtime failures due to method signature changes or other class differences. This change adds a manifest attribute to specify a 'requires' version which is a minmum system version. It also introduces a method to specify the system version of the plugin manager and logic to disable plugins on load if the system version is too old. This works for both loadPlugins() and loadPlugin().
* Merge pull request #13 from gitblit/descriptionDecebal Suiu2014-04-122-20/+39
|\ | | | | Add an optional description to the manifest
| * Add an optional description to the manifestJames Moger2014-04-122-20/+39
| |
* | Change log level of a debug message from warn to debugJames Moger2014-04-121-1/+1
|/
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2014-04-111-2/+2
|
* [maven-release-plugin] prepare release release-0.7.1release-0.7.1Decebal Suiu2014-04-111-2/+2
|
* Allow disabled plugins to be unloaded and deletedJames Moger2014-04-101-6/+7
|
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2014-04-101-2/+2
|
* [maven-release-plugin] prepare release release-0.7.0release-0.7.0Decebal Suiu2014-04-101-2/+2
|
* Allow inspection of disabled plugins by not stopping resource loadingJames Moger2014-04-092-30/+12
| | | | | | | | | | | | | | The differences between a DISABLED plugin and a STARTED plugin are: 1. a STARTED plugin has executed Plugin.start(), a DISABLED plugin has not 2. a STARTED plugin may contribute extension instances, a DISABLED plugin may not DISABLED plugins still have valid classloaders and their classes can be manually loaded and explored, but the resource loading - which is important for inspection has been handicapped by the DISABLED check. Instead of preventing loading the extension indexes for DISABLED plugins, the extension finder should only return ExtensionWrappers for STARTED plugins.
* add listeners to plugin state changesDecebal Suiu2014-04-098-53/+186
|
* use PluginState.DISABLE instead of PluginManger.isPluginDisabled()Decebal Suiu2014-04-084-47/+21
|
* added support for PluginManager.getExtensionClassNames(String pluginId) and ↵Decebal Suiu2014-04-087-131/+220
| | | | simplify enable/disable plugin
* a first version related to enable-disable pluginDecebal Suiu2014-04-076-58/+209
|
* Implement loading a single plugin archiveJames Moger2014-04-044-635/+691
|
* Simplify changes per reviewJames Moger2014-04-041-9/+7
|
* Implement delete pluginJames Moger2014-04-033-22/+104
|
* Merge pull request #3 from gitblit/stop_pluginDecebal Suiu2014-04-034-60/+192
|\ | | | | Add support for starting, stopping, and unloading a plugin
| * Add method to unload a plugin and it's dependenciesJames Moger2014-04-023-8/+59
| |
| * Add methods to start & stop a single plugin and it's dependenciesJames Moger2014-04-023-52/+133
| |
* | adopt semantic versioning for pluginDecebal Suiu2014-04-012-89/+51
| |
* | adopt semantic versioningDecebal Suiu2014-04-011-2/+2
| |
* | make PluginException visible from outside (public)Decebal Suiu2014-03-311-1/+1
| |
* | check that a java type is an ExtensionPointDecebal Suiu2014-03-311-8/+19
|/
* fix a minor message format in loggingDecebal Suiu2014-03-311-1/+1
|
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2013-10-111-2/+2
|
* [maven-release-plugin] prepare release release-0.6release-0.6Decebal Suiu2013-10-111-2/+2
|
* add possibility to override extension creation in DefaultExtensionFinderDecebal Suiu2013-10-101-8/+40
|
* remove sezpoz dependencyDecebal Suiu2013-10-107-95/+240
|
* add RuntimeMode with DEVELOPMENT and DEPLOYMENT values and working on ↵Decebal Suiu2013-10-036-397/+573
| | | | DEVELOPMENT mode
* [maven-release-plugin] prepare for next development iterationDecebal Suiu2013-09-261-2/+2
|
* [maven-release-plugin] prepare release release-0.5release-0.5Decebal Suiu2013-09-261-2/+2
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-07 02:52:09 +0000