Acme-CPANModules-PERLANCAR-PluginSystem
view release on metacpan or search on metacpan
},
{
"class" : "Dist::Zilla::Plugin::ShareDir",
"name" : "@Author::PERLANCAR/@Filter/ShareDir",
"version" : "6.030"
},
{
"class" : "Dist::Zilla::Plugin::MakeMaker",
"config" : {
"Dist::Zilla::Role::TestRunner" : {
"default_jobs" : 1
}
},
"name" : "@Author::PERLANCAR/@Filter/MakeMaker",
"version" : "6.030"
},
{
"class" : "Dist::Zilla::Plugin::Manifest",
"name" : "@Author::PERLANCAR/@Filter/Manifest",
"version" : "6.030"
},
name: '@Author::PERLANCAR/@Filter/ExecDir'
version: '6.030'
-
class: Dist::Zilla::Plugin::ShareDir
name: '@Author::PERLANCAR/@Filter/ShareDir'
version: '6.030'
-
class: Dist::Zilla::Plugin::MakeMaker
config:
Dist::Zilla::Role::TestRunner:
default_jobs: 1
name: '@Author::PERLANCAR/@Filter/MakeMaker'
version: '6.030'
-
class: Dist::Zilla::Plugin::Manifest
name: '@Author::PERLANCAR/@Filter/Manifest'
version: '6.030'
-
class: Dist::Zilla::Plugin::ConfirmRelease
name: '@Author::PERLANCAR/@Filter/ConfirmRelease'
version: '6.030'
(Plugin::System). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of
this particular plugin style:
* a plugin can be installed more than once and parameterized (like in
Dist::Zilla or Pod::Weaver) [flexibility];
* execution order of plugins is by priority, then by its order of
activation;
* a plugin has a default priority value but the value can be overriden
by user [flexibility];
* a plugin has a default event in which it participates, but user can
overrides this [flexibility];
* support for repeating an event [flexibility];
* support for skipping (aborting) an event [flexibility];
ACME::CPANMODULES ENTRIES
Plugin::System
The current name of what the plugin system will be refactored into.
lib/Acme/CPANModules/PERLANCAR/PluginSystem.pm view on Meta::CPAN
description => <<'_',
This is a personal list of my modules/frameworks which use a particular plugin
system style which I will someday extract into its own framework
(<pm:Plugin::System>). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of this
particular plugin style:
* a plugin can be installed more than once and parameterized (like in <pm:Dist::Zilla> or <pm:Pod::Weaver>) [flexibility];
* execution order of plugins is by priority, then by its order of activation;
* a plugin has a default priority value but the value can be overriden by user [flexibility];
* a plugin has a default event in which it participates, but user can overrides this [flexibility];
* support for repeating an event [flexibility];
* support for skipping (aborting) an event [flexibility];
_
entries => [
{
module => 'Plugin::System',
description => <<'_',
lib/Acme/CPANModules/PERLANCAR/PluginSystem.pm view on Meta::CPAN
(L<Plugin::System>). (And I am also slowly converting more of my
plugin-supporting projects to use this style). Some of the features of this
particular plugin style:
=over
=item * a plugin can be installed more than once and parameterized (like in L<Dist::Zilla> or L<Pod::Weaver>) [flexibility];
=item * execution order of plugins is by priority, then by its order of activation;
=item * a plugin has a default priority value but the value can be overriden by user [flexibility];
=item * a plugin has a default event in which it participates, but user can overrides this [flexibility];
=item * support for repeating an event [flexibility];
=item * support for skipping (aborting) an event [flexibility];
=back
=head1 ACME::CPANMODULES ENTRIES
=over
( run in 1.132 second using v1.01-cache-2.11-cpan-0a6323c29d9 )