[
https://issues.apache.org/jira/browse/LOG4PHP-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220241#comment-13220241
]
Ivan Habunek commented on LOG4PHP-173:
--------------------------------------
Hi Bruce,
First of all, I'd like to point out that PHP 5.2.17 is the last release from
the 5.2 branch. Can you please double-check which version you're using.
http://www.php.net/downloads.php
Second, PHPunit 3.6 which we use for testing is compatible with PHP 5.2.7+.
https://github.com/sebastianbergmann/phpunit
We test the releases on 5.2.17 and the latest from 5.3.x branch.
I have just now manually tried the first example from the quick start guide on
log4php 2.2.1 with the following PHP versions: 5.2.7 (Windows), 5.2.17 (Linux)
and 5.3.8 (Windows). It works the same on all three and I am unable to
reproduce the error which you reported.
It is possible that it's an issue with PEAR. Can you try to download the source
package from our web and try it on that? In case the pear package has somehow
become corrupted.
Regards,
Ivan
> Minimum PHP version requirement
> -------------------------------
>
> Key: LOG4PHP-173
> URL: https://issues.apache.org/jira/browse/LOG4PHP-173
> Project: Log4php
> Issue Type: Dependency upgrade
> Components: Documentation
> Affects Versions: 2.2.1
> Environment: PHP v5.2.26
> Reporter: Bruce Ingalls
> Labels: documentation
> Fix For: 2.2.1
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Documentation claims that Log4php supports PHP v5.2. The simplest example in
> quickstart works for v5.3, but fails for v5.2.26:
> Fatal error: Call to a member function close() on a non-object in
> ~PEAR/log4php/Logger.php on line 302
> Further, your unit testing section at
> http://wiki.apache.org/logging-log4php/WritingTests uses phpunit, which
> requires PHP v5.2.27+
> This implies that you are not testing older versions of PHP, unless you've
> built a legacy test harness.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
