Kwalitee Issues

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Dist::Zilla::Role::AfterBuild
  • Dist::Zilla::Role::AfterMint
  • Dist::Zilla::Role::AfterRelease
  • Dist::Zilla::Role::BeforeArchive
  • Dist::Zilla::Role::BeforeBuild
  • Dist::Zilla::Role::BeforeMint
  • Dist::Zilla::Role::BeforeRelease
  • Dist::Zilla::Role::BuildRunner
  • Dist::Zilla::Role::ConfigDumper
  • Dist::Zilla::Role::FileFinder
  • Dist::Zilla::Role::FileGatherer
  • Dist::Zilla::Role::FileMunger
  • Dist::Zilla::Role::FilePruner
  • Dist::Zilla::Role::InstallTool
  • Dist::Zilla::Role::MetaProvider
  • Dist::Zilla::Role::MintingProfile
  • Dist::Zilla::Role::ModuleMaker
  • Dist::Zilla::Role::PrereqSource
  • Dist::Zilla::Role::Releaser
  • Dist::Zilla::Role::ShareDir
  • Dist::Zilla::Role::TestRunner
  • Dist::Zilla::Role::VersionProvider
  • Moose
  • Moose::Autobox

main_module_version_matches_dist_version

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

has_meta_json

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

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).

Modules

Name Abstract Version View
Dist::Zilla::Plugin::ReportPhase Report whats going on. metacpan

Other Files

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