VCS-CMSynergy 1.31
- Released by
- RSCHUPP
- Version
- Release Date
- 2008-02-01
- Kwalitee
- 137.5
- Core Kwalitee
- 87.5
- LINKS
VCS-CMSynergy 1.31 Deleted
Kwalitee Issues
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- buildtool_not_executable
-
Change the permissions of Build.PL/Makefile.PL to not-executable.
- 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: VCS::CMSynergy::Helper, VCS::CMSynergy::ObjectTieHash, VCS::CMSynergy::Users, VCS::CMSynergy::update_users
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: VCS-CMSynergy-1.31/lib/VCS/CMSynergy/Changes.pod -- Around line 260: Non-ASCII character seen before =encoding in 'Jürgen'. Assuming CP1252 VCS-CMSynergy-1.31/lib/VCS/CMSynergy/Client.pm -- Around line 974: Expected text after =item, not a number Around line 979: Expected text after =item, not a number Around line 983: Expected text after =item, not a number VCS-CMSynergy-1.31/lib/VCS/CMSynergy/Project.pm -- Around line 667: Non-ASCII character seen before =encoding in 'projectâs'. Assuming UTF-8
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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: VCS::CMSynergy, VCS::CMSynergy::Client, VCS::CMSynergy::Helper, VCS::CMSynergy::Object, VCS::CMSynergy::ObjectTieHash, VCS::CMSynergy::Project, VCS::CMSynergy::Users, VCS::CMSynergy::update_users
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 1,1.31
- 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 |
|---|---|---|---|
| VCS::CMSynergy | Perl interface to Telelogic Synergy | 1.31 | metacpan |
| VCS::CMSynergy::Client | base class for CM Synergy methods that don't require a session | 1 | metacpan |
| VCS::CMSynergy::Helper | ancillary convenience functions | 1 | metacpan |
| VCS::CMSynergy::Object | convenience wrapper to treat objectnames as an object | 1 | metacpan |
| VCS::CMSynergy::ObjectTieHash | 1 | metacpan | |
| VCS::CMSynergy::Project | convenience methods for C<VCS::CMSynergy::Object>s of type C<"project"> | 1 | metacpan |
| VCS::CMSynergy::Users | Perl interface to CM Synergy user administration | 1 | metacpan |