New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning causing problems #8
Comments
Of course, if I don't set AUTHOR_TESTING then the Pod-Spell build succeeds but it doesn't look good with the warnings anyway ;-) |
Now that Path::FindDev uses Class::Tiny as well, it's producing warnings too:
|
Thanks for the bug report. I'd imaging thats So two questions,
I mean, I don't do anything directly with |
Actually, I think I have an idea ... its probably that you're using one of those annoying versions of something in the testing stack that turns additional warnings on globally, even for things that didn't ask for it. Its still a bug, ... just working out where and what the right solution is is the hard part. |
I'm afraid I'm already using Class::Tiny 0.009 and when I used Carp::Always I got exactly the same diagnostics, nothing extra. Sorry about that. |
Fixed in Class::Tiny 0.010 being shipped to CPAN now. |
Works for me, thanks. |
Fixed dependencies should exist for anyone who uses IsDev>=0.3.2 or FindDev>=0.3.1. Thanks for reporting. |
Not sure if this is a bug in F:S:P or further down, but I see this when running the test suite:
After installing the dist anyway and then trying to build Pod::Spell, which has just introduced use of F:S:P, the test suite now fails (didn't with F:S:P 0.4.4):
The text was updated successfully, but these errors were encountered: