Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Dist-Zilla-Plugin-ContributorsFile CPAN distribution.

Report information
The Basics
Id: 95626
Status: resolved
Priority: 0/
Queue: Dist-Zilla-Plugin-ContributorsFile

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc: ether [...] cpan.org
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.2.0
Fixed in: (no value)



Subject: Can't locate object method "contributor_list" via package "Dist::Zilla::Plugin::ContributorsFromGit"
While trying to build a dzil-based distribution (Prophet) I ran into the following problem: Can't locate object method "contributor_list" via package "Dist::Zilla::Plugin::ContributorsFromGit" at /usr/perl5.18.2/lib/site_perl/5.18.2/Dist/Zilla/Plugin/ContributorsFile.pm line 41. It seems that Dist::Zilla::Plugin::ContributorsFromGit made an attribute private with this commit: commit 369b8e38ec5ef490bbb08df80bec69a4d4a1ab28 Author: Chris Weyl <cweyl@alumni.drew.edu> Date: Tue Apr 8 15:37:38 2014 -0700 Flag our attributes as private ...as they are -- we're not a stash, after all :) (Yet?) Regards, Slaven
On 2014-05-13 15:12:34, SREZIC wrote: Show quoted text
> While trying to build a dzil-based distribution (Prophet) I ran into > the following problem: > > Can't locate object method "contributor_list" via package > "Dist::Zilla::Plugin::ContributorsFromGit" at > /usr/perl5.18.2/lib/site_perl/5.18.2/Dist/Zilla/Plugin/ContributorsFile.pm > line 41.
Instead of calling the plugin's code directly to get the contributor list, you can simply get it from $self->zilla->distmeta->{x_contributors} -- that will let you use any of the contributors-providing plugins, rather than relying on just one (e.g. there is a plugin that manually populates the contributor list). Just make sure to not call ->distmeta until the FileMunging state or later -- calling it sooner will result in an incomplete distmeta and probably make some other plugins unhappy about having their 'metadata' subs called too early.
Patched. Thanks to you both!