Kwalitee Issues

use_strict

Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.

Error: PXP::I18N

main_module_version_matches_dist_version

Make sure that the main module name and version are the same of the distribution.

no_pod_errors

Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.

Error: PXP-0.1.2/lib/PXP/Config.pm -- Around line 84: You can't have =items (as at line 123) unless the first thing after the =over is an =item PXP-0.1.2/lib/PXP/Extension.pm -- Around line 130: You forgot a '=back' before '=head1' PXP-0.1.2/lib/PXP/ExtensionPoint.pm -- Around line 153: You forgot a '=back' before '=head1' PXP-0.1.2/lib/PXP/ExtensionPointClass.pm -- Around line 47: '=item' outside of any '=over' =over without closing =back PXP-0.1.2/lib/PXP/Plugin.pm -- Around line 476: You forgot a '=back' before '=head1' PXP-0.1.2/lib/PXP/PluginRegistry.pm -- Around line 69: '=item' outside of any '=over' PXP-0.1.2/lib/PXP.pm -- Around line 175: Non-ASCII character seen before =encoding in 'Aurélien'. Assuming UTF-8

meta_yml_declares_perl_version

If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.

has_meta_json

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

meta_yml_has_license

Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.

use_warnings

Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: PXP::I18N

meta_yml_has_provides

Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.

meta_yml_has_repository_resource

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

has_separate_license_file

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.

Modules

Name Abstract Version View
PXP Perl Xtensions & Plugins 0.1 metacpan
PXP::Config metacpan
PXP::Extension Extension model class (used only in the internal registry) metacpan
PXP::ExtensionPoint ExtensionPoint model class (used only in the internal registry) metacpan
PXP::ExtensionPointClass Basic logic and Mandatory interfaces for L<PXP::ExtensionPoint>s. metacpan
PXP::I18N metacpan
PXP::Plugin Plugin class definition (used only in the internal registry) metacpan
PXP::PluginRegistry Registry of plugins for PXP 0.1 metacpan

Other Files

Changes metacpan
MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan