RMI v0.07
- Released by
- SAKOHT
- Version
- Release Date
- 2009-10-22
- Kwalitee
- 138.71
- Core Kwalitee
- 93.55
- LINKS
RMI v0.07
Kwalitee Issues
- manifest_matches_dist
-
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error:
- MANIFEST (69) does not match dist (41):
- Missing in Dist: RMI-v0.07/Changes, RMI-v0.07/INSTALL, RMI-v0.07/LICENSE, RMI-v0.07/Makefile.PL, RMI-v0.07/README, RMI-v0.07/lib/RMI.pm, RMI-v0.07/lib/RMI/Client.pm, RMI-v0.07/lib/RMI/Client/ForkedPipes.pm, RMI-v0.07/lib/RMI/Client/Tcp.pm, RMI-v0.07/lib/RMI/Node.pm, RMI-v0.07/lib/RMI/ProxyObject.pm, RMI-v0.07/lib/RMI/ProxyReference.pm, RMI-v0.07/lib/RMI/Server.pm, RMI-v0.07/lib/RMI/Server/ForkedPipes.pm, RMI-v0.07/lib/RMI/Server/Tcp.pm, RMI-v0.07/prove-all.sh, RMI-v0.07/t/04_use_remote.t, RMI-v0.07/t/06_client_server_pairs.t, RMI-v0.07/t/RMI/TestClass1.pm, RMI-v0.07/t/RMI/TestClass2.pm, t/01_basic.t, t/02_unblessed_refs.t, t/03_exceptions.t, t/05_use_lib_remote.t, t/07_as_documented.t, t/08_wantarray.t, t/09_bind_variables.t, t/RMI/TestClass.pm
- 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: RMI::TestClass
- 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.
- proper_libs
-
Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.
Error: RMI-v0.07/t/RMI/TestClass.pm
- 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: RMI::TestClass
- 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.001000,0.007000
- 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 |
|---|---|---|---|
| RMI | Remote Method Invocation with transparent proxies v0.07 | 0.007000 | metacpan |
| RMI::Client | connection to an RMI::Server | 0.001000 | metacpan |
| RMI::Client::ForkedPipes | an RMI::Client implementation with a private out-of-process server | 0.001000 | metacpan |
| RMI::Client::Tcp | an RMI::Client implementation using TCP/IP sockets | 0.001000 | metacpan |
| RMI::Node | base class for RMI::Client and RMI::Server | 0.001000 | metacpan |
| RMI::ProxyObject | used internally by RMI for "stub" objects | 0.001000 | metacpan |
| RMI::ProxyReference | used internally by RMI to tie references | 0.001000 | metacpan |
| RMI::Server | service RMI::Client requests from another process | 0.001000 | metacpan |
| RMI::Server::ForkedPipes | service RMI::Client::ForkedPipes requests | 0.001000 | metacpan |
| RMI::Server::Tcp | service RMI::Client::Tcp requests | 0.001000 | metacpan |
| RMI::TestClass | metacpan |