Re: Convincing Dist::Zilla to use a different Pod::Coverage class

There seems to be Dist::Zilla::Plugin::Test::Pod::Coverage::Configurable (found via Dist::Zilla coverage).

I'm not in the camp of people saying that Dist::Zilla would make life easier. It seems to solve problems that I don't have, and it certainly creates problems for me, as I can't easily run tests for the repository checkout of a module modify it without buying into the Dist::Zilla mechanism myself.

Comment on Re: Convincing Dist::Zilla to use a different Pod::Coverage class

Replies are listed 'Best First'.
Re^2: Convincing Dist::Zilla to use a different Pod::Coverage class by pokki (Monk) on Dec 15, 2014 at 16:35 UTC
Aah, this looks exactly like what I need, at least for the POD coverage. I'm not in the camp of people saying that Dist::Zilla would make life easier. It seems to solve problems that I don't have, and it certainly creates problems for me, as I can't easily run tests for the repository checkout of a module modify it without buying into the Dist::Zilla mechanism myself. Yes, this is my general experience as well. It works fine as long as you're working exactly like the first person to write the dist.ini does, but it's not flexible enough to cover the rest of the use cases. For instance, using good old prove, plus TAP::Formatter::JUnit, I can emit JUnit XML and make Jenkins happy, but I can't figure how to use custom formatters with Dist::Zilla. Thanks for the save!	[reply]

Replies are listed 'Best First'.

Re^2: Convincing Dist::Zilla to use a different Pod::Coverage class
by pokki (Monk) on Dec 15, 2014 at 16:35 UTC

Aah, this looks exactly like what I need, at least for the POD coverage.

I'm not in the camp of people saying that Dist::Zilla would make life easier. It seems to solve problems that I don't have, and it certainly creates problems for me, as I can't easily run tests for the repository checkout of a module modify it without buying into the Dist::Zilla mechanism myself.

Yes, this is my general experience as well. It works fine as long as you're working *exactly* like the first person to write the dist.ini does, but it's not flexible enough to cover the rest of the use cases. For instance, using good old prove, plus TAP::Formatter::JUnit, I can emit JUnit XML and make Jenkins happy, but I can't figure how to use custom formatters with Dist::Zilla.

Thanks for the save!

[reply]