Hi Inderpal
The name of your module is a bad choice. All Perl modules are ... Perl
modules! There is no need to put the words 'Perl' or 'Module' in the
name of a Perl module. I.e. don't ever do that - PLEASE!
Your chosen name tells us nothing about it's purpose nor the context in
which it might be used. And when it's indexed by CPAN, how can we
possibly search for it? I.e. How can we know what to search for, since
we can't even guess such an odd name. And we can't search for generic
words such as Perl or module, can we :-)?
For help with naming modules, see:
https://pause.perl.org/pause/query?ACTION=pause_namingmodules
And from the source I see you're referring to a whole set of other modules:
package OxdPerlModule;
use 5.006;
use strict;
use warnings FATAL => 'all';
use OxdPackages::OxdConfig;
use OxdPackages::OxdRegister;
use OxdPackages::UpdateRegistration;
use OxdPackages::GetAuthorizationUrl;
use OxdPackages::GetTokenByCode;
use OxdPackages::GetUserInfo;
use OxdPackages::OxdLogout;
use OxdPackages::UmaRsProtect;
use OxdPackages::UmaRpAuthorizeRpt;
use OxdPackages::UmaRpGetGat;
use OxdPackages::UmaRpGetRpt;
use OxdPackages::UmaRsCheckAccess;
They are not on CPAN, are they, so what on Earth is going on? People who
use CPAN have an expectation that /all/ modules you upload will only use
modules available from CPAN (or ship with Perl itself).
IOW (In Other Words) modules you /don't/ upload can use your own module
of course, but when someone downloads your module from CPAN - say for
automated testing - they expect it to depend exclusively on modules
shipped with Perl or available on CPAN.
And even this text in your module is utterly uninformative :-((:
=head1 NAME
OxdPerlModule - The great new OxdPerlModule!
Here's a list of my modules:
https://metacpan.org/author/RSAVAGE
Look carefully at how the names are structured, so they form
hierarchies, and so people can guess while searching on CPAN even if
they don't know the exact name.
Good luck for next time....
--
Ron Savage - savage.net.au
