SAP-BC-XMLRFC 0.06 Latest
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
Add =head1 LICENSE and the text of the license to the main module in your code.
List all used modules in META.yml requires
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: SAP-BC-XMLRFC-0.06/lib/SAP/BC.pm -- Around line 34: You can't have =items (as at line 66) unless the first thing after the =over is an =item
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Add tests or move tests.pl to the t/ directory!
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.
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
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: SAP::BC, SAP::BC::Iface, SAP::BC::XMLRFC
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
|SAP::BC||Interface to SAP's Business Connector||0.03||metacpan|
|SAP::BC::Iface||Perl extension for parsing and creating an Interface Object. The interface object would then be passed to the SAP::BC::XMLRFC object to carry out the actual call, and return of values.||0.03||metacpan|
|SAP::BC::XMLRFC||Perl extension for performing RFC Function calls against an SAP R/3 using the Business Connector System. Please refer to the README file found with this distribution.||0.06||metacpan|