File Coverage

blib/lib/Test/BrewBuild/Plugin/DefaultExec.pm

Criterion	Covered	Total	%
statement	12	12	100.0
branch	1	2	50.0
condition			n/a
subroutine	2	2	100.0
pod	0	1	0.0
total	15	17	88.2

package Test::BrewBuild::Plugin::DefaultExec;

# default exec command set plugin for Test::BrewBuild

our $VERSION = '2.11';

my $state = bless {}, __PACKAGE__;

sub brewbuild_exec{
    shift; # throw away class
    my $log = shift;
    my $clog = $log->child( __PACKAGE__.'::brewbuild_exec' );
    $clog->_6( 'performing plugin duties' );
    return _cmd();
}
sub _cmd {
    my $module = shift;

    #FIXME: we have to do the below nonsense, because DATA can't
    # be opened twice if we get called more than once per run

    if (! defined $state->{raw}){
        @{ $state->{raw} } = ;
    }

    my @cmd = @{ $state->{raw} };

    return @cmd;
}
1;

=pod

=head1 NAME

Test::BrewBuild::Plugin::DefaultExec - The default 'exec' command plugin.

=head1 SYNOPSIS

To use, if you've actually installed your plugin:

    brewbuild --plugin My::ExecPlugin

If you have it in a local directory (ie. not installed) (note the path can be
relative):

    brewbuild --plugin /path/to/ExecPlugin.pm

Send in arguments to your plugin. The C<--args, -a> flag sets an array. For
each argument, C is called once, passing in the next element of the
array.

    berrybrew -p My::Plugin --args 1 -a 2

=head1 CREATION

To create a temporary or test plugin, simply create a C<*.pm> file just like
this one with the same subroutine, and in the C<__DATA__> section, include the
code you need executed by C<*brew exec>.

The first argument you will receive is the C log object of
the core L. You can ignore this, or create a child and log
throughout your plugin.

=head1 AUTHOR

Steve Bertrand, C<<  >>

=cut

__DATA__