github/pf4j - pf4j - 帆软第三方插件仓库

Commit Graph

Author	SHA1	Message	Date
Mário Franco	78c7321e85	Prepare unit test coverage on Travis and Coveralls	10 years ago
Decebal Suiu	1b00a01b61	fix wildcard import	10 years ago
Decebal Suiu	302ec57f15	fix for #53	10 years ago
Mário Franco	dff2c20814	Stop leafs first	10 years ago
Mário Franco	e4cf827a4c	Fix #42 and it's a help for #32	10 years ago
Decebal Suiu	7aa50bf83d	make pluginsDirectory canonical	10 years ago
Decebal Suiu	96401ef9a8	fix typo	10 years ago
Mário Franco	f3fe919089	Replace Version with semver lib	10 years ago
Decebal Suiu	e159468196	little preparation for #42	10 years ago
Mário Franco	1f14178942	Fix name in utf	10 years ago
Decebal Suiu	9416698908	fix type	10 years ago
Decebal Suiu	aee82c92b0	convert existing generics to diamond syntax	10 years ago
Mário Franco	86a38894c2	Editor config style applied	10 years ago
Decebal Suiu	56a7ee47ac	review #41	10 years ago
Mário Franco	966e5d506b	Clean PluginStatusProvider api	10 years ago
Mário Franco	3720dddcd5	Add Plugin status provider	10 years ago
Decebal Suiu	7ae4ccd263	specify that PluginClassLoader is a Parent Last ClassLoader - it loads the classes from the plugin's jars before delegating to the parent class loader	10 years ago
Decebal Suiu	579bae7c3d	defense for #21	10 years ago
Decebal Suiu	357bdf703f	try to improve logging for DefaultExtensionFinder	11 years ago
Decebal Suiu	187ffc9b3e	[maven-release-plugin] prepare for next development iteration	11 years ago
Decebal Suiu	54b1f59c9b	[maven-release-plugin] prepare release release-0.9.0	11 years ago
Decebal Suiu	808a36a3ae	try to resolve issue #20	11 years ago
Decebal Suiu	e58e71a098	load extensions from classpath; before this commit only plugins can declare extensions	11 years ago
Decebal Suiu	f508484004	fix an issue that occurs when the plugin developer put the pf4j jar in the plugin's lib folder (or not declare the pf4j dependency with scope provided in pom.xml)	11 years ago
Decebal Suiu	441062e98c	minor change	11 years ago
Decebal Suiu	69835a1406	add info message about pf4j version and the runtime mode	11 years ago
Decebal Suiu	90aefdd121	add version in DefaultPluginManager	11 years ago
Decebal Suiu	77c4e00469	add dispose method in PluginClassLoader	11 years ago
Decebal Suiu	57436d67b4	[maven-release-plugin] prepare for next development iteration	11 years ago
Decebal Suiu	a20a13700f	[maven-release-plugin] prepare release release-0.8.0	11 years ago
Decebal Suiu	7df691ccec	update slf4j to 1.7.5	11 years ago
Decebal Suiu	eb24fa2b32	rename PluginVersion to Version	11 years ago
James Moger	316109a558	Move requires logic to isPluginValid(PluginWrapper), rename default version to ZERO	11 years ago
James Moger	eba6d3dc6b	Add an optional requires manifest value 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().	11 years ago
James Moger	2bc87639f9	Add an optional description to the manifest	11 years ago
James Moger	361a974759	Change log level of a debug message from warn to debug	11 years ago
Decebal Suiu	ae2c0cd69f	[maven-release-plugin] prepare for next development iteration	11 years ago
Decebal Suiu	bd953f99a3	[maven-release-plugin] prepare release release-0.7.1	11 years ago
James Moger	e996639f47	Allow disabled plugins to be unloaded and deleted	11 years ago
Decebal Suiu	726c5cab70	[maven-release-plugin] prepare for next development iteration	11 years ago
Decebal Suiu	2533d78213	[maven-release-plugin] prepare release release-0.7.0	11 years ago
James Moger	e80ae32868	Allow inspection of disabled plugins by not stopping resource loading 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.	11 years ago
Decebal Suiu	7e00f212b1	add listeners to plugin state changes	11 years ago
Decebal Suiu	33baceffd7	use PluginState.DISABLE instead of PluginManger.isPluginDisabled()	11 years ago
Decebal Suiu	0cf3fc42ff	added support for PluginManager.getExtensionClassNames(String pluginId) and simplify enable/disable plugin	11 years ago
Decebal Suiu	746ac803b8	a first version related to enable-disable plugin	11 years ago
James Moger	de6b7df7a6	Implement loading a single plugin archive	11 years ago
James Moger	c2fe1da412	Simplify changes per review	11 years ago
James Moger	c867d45898	Implement delete plugin	11 years ago
James Moger	4fefdcf76c	Add method to unload a plugin and it's dependencies	11 years ago

... 2 3 4 5 6

297 Commits (7d9f6a012bee888333e11c1284e41ea472e1838a)