Kwalitee Issues

has_meta_yml

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

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: RevML::Doctype::v0_26, RevML::Doctype::v0_27, RevML::Doctype::v0_28

prereq_matches_use

List all used modules in META.yml requires

Error:

  • IPC::Run
  • Regexp::Shellish
  • XML::AutoWriter
  • XML::Doctype
  • XML::Parser

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: VCP-0.068/lib/RevML/Doctype.pm -- Around line 194: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Debug.pm -- Around line 185: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Dest/cvs.pm -- Around line 271: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Dest.pm -- Around line 58: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Plugin.pm -- Around line 88: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Revs.pm -- Around line 167: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Source/p4.pm -- Around line 705: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP/Source.pm -- Around line 64: You forgot a '=back' before '=head1' VCP-0.068/lib/VCP.pm -- Around line 133: You forgot a '=back' before '=head1'

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.

has_known_license_in_source_file

Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

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: RevML::Doctype, RevML::Doctype::v0_26, RevML::Doctype::v0_27, RevML::Doctype::v0_28, RevML::Writer, VCP, VCP::Debug, VCP::Dest, VCP::Dest::cvs, VCP::Dest::p4, VCP::Dest::revml, VCP::Plugin, VCP::Rev, VCP::Revs, VCP::Source, VCP::Source::cvs, VCP::Source::p4, VCP::Source::revml, VCP::TestUtils

test_prereq_matches_use

List all modules used in the test suite in META.yml test_requires

Error:

  • IPC::Run

consistent_version

Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).

Error: 0.1,1

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
RevML::Doctype A subclass of XML::Doctype 0.1 metacpan
RevML::Doctype::v0_26 metacpan
RevML::Doctype::v0_27 metacpan
RevML::Doctype::v0_28 metacpan
RevML::Writer Write RevML files using the RevML DTD 0.1 metacpan
VCP Versioned Copy, copying hierarchies of versioned files 0.1 metacpan
VCP::Debug debugging support for VCP 0.1 metacpan
VCP::Dest A base class for VCP destinations 0.1 metacpan
VCP::Dest::cvs cvs destination driver 1 metacpan
VCP::Dest::p4 p4 destination driver 1 metacpan
VCP::Dest::revml Outputs versioned files to a revml file 0.1 metacpan
VCP::Plugin A base class for VCP::Source and VCP::Dest 0.1 metacpan
VCP::Rev VCP's concept of a revision 1 metacpan
VCP::Revs A collection of VCP::Rev objects. 1 metacpan
VCP::Source A base class for repository sources 0.1 metacpan
VCP::Source::cvs A CVS repository source 1 metacpan
VCP::Source::p4 A Perforce p4 repository source 1 metacpan
VCP::Source::revml Outputs versioned files to a revml file 0.1 metacpan
VCP::TestUtils support routines for VCP testing metacpan

Other Files

MANIFEST metacpan
Makefile.PL metacpan
README metacpan