Ivan Habunek created LOG4PHP-220:
Summary: Allow deep indexes in superglobal pattern converters
Key: LOG4PHP-220
URL: https://issues.apache.org/jira/browse/LOG4PHP-220
Project: Log4php
Issue
for log4php tests is no good - unittest
> must be unit.
>
>
> 2014-05-19 11:28 GMT+04:00 Florian Semm :
>
> Hey,
>>
>> is the vagrant configuration still an issue? If so I would like to create
>> a setup for the unittest.
>>
>>
>> Regards
&g
te:
> I don't think we need to support older versions of the driver. As of next
> release, we will only support
> latest driver API from php5.5. I am okay with that decision.
>
> LOG4PHP-219 noted, what is the release date of new log4php version ? (how
> much time do I have)
Ivan Habunek created LOG4PHP-219:
Summary: Problems with the mongodb appender
Key: LOG4PHP-219
URL: https://issues.apache.org/jira/browse/LOG4PHP-219
Project: Log4php
Issue Type: Bug
Hi Vladimír,
I'm working on a new release of log4php and having issues with the mongodb
appender.
Running tests on php5.5 with php-mongo driver 1.4.5. produces warnings
which break tests. I have created an issue for this:
https://issues.apache.org/jira/browse/LOG4PHP-219
Do you think we need to
riy Ulyanov wrote:
> Hi, Ivan!
>
> I see that you merged all my pull requests to develop. That's great news!
> Can i help you with assembling 2.4?
> May be you have some foreground tickets with which i can help? Logstash?
> PSR-3? :)
>
>
> 2014-04-26 21:58 GMT+04:0
that we can asseble 2.4.0 in this month.
>>
>> Until we didn't include graylog2 appenders into library people can
>> install it using composer:
>> https://packagist.org/packages/dulyanov/log4php-graylog2
>>
>>
>>
>> 2014-04-20 22:30 GMT+04:00 Iv
apache/logging-log4php/pull/10
> https://github.com/apache/logging-log4php/pull/11
>
> Please, check it :)
> When can we assemble 2.4.0?
>
>
> 2014-02-24 18:38 GMT+04:00 Ivan Habunek :
>
> There's a contributor workfow here:
>> http://wiki.apache.org/loggi
[
https://issues.apache.org/jira/browse/LOG4PHP-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968405#comment-13968405
]
Ivan Habunek commented on LOG4PHP-218:
--
Could you please report the proble
gt; My last question is about development flow:
> What is the "develop" branch?
> Is it correct that "master" contains last stable version?
> From what branch should I fork? From "master"?
>
>
> 2014-02-24 18:12 GMT+04:00 Ivan Habunek :
>
> Sorry, I was
have any questions.
Regards,
Ivan
On 24 February 2014 14:57, Ivan Habunek wrote:
> You can write docs here:
> https://github.com/apache/logging-log4php/tree/develop/docs
>
> Put version 2.4.0 in docs. That will be the next release. We will work on
> 3.0 after.
>
> I will
reate Gelf layout with unit tests, may be on next
> week.
>
>
> On Monday, February 24, 2014, Ivan Habunek wrote:
>
>> Hey Dmitriy,
>>
>> Thank you for the contrubution, it looks great. Unfortunately, I'll be
>> out of the country until late next month
Hey Dmitriy,
Thank you for the contrubution, it looks great. Unfortunately, I'll be out
of the country until late next month.
I will have some changes in my working schedule (for the better) and hope
to find some time to work on a release in April.
Regards,
Ivan
On 23 February 2014 22:57, Dmit
ging-log4php%2Ftree%2Ftravis-ci&url_id=305c3b6599d6a0254984d50ec0e2e79ce1e7f836>
> )
>Build #2
> failed.<http://clicks.travis-ci.org/track/click.php?u=30007208&id=e691403a33cf436d8d366477b60280ba&url=https%3A%2F%2Ftravis-ci.org%2Fapache%2Flogging-log4php%2Fbuilds%2F15572023&url_id=5ca76ac97d9bca
[
https://issues.apache.org/jira/browse/LOG4PHP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-205.
--
Resolution: Fixed
Fix Version/s: develop
> debug_backtrace() sometimes do not ret
[
https://issues.apache.org/jira/browse/LOG4PHP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reassigned LOG4PHP-205:
Assignee: Ivan Habunek
> debug_backtrace() sometimes do not return 'file&#x
[
https://issues.apache.org/jira/browse/LOG4PHP-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-206.
Resolution: Duplicate
> CLONE - debug_backtrace() sometimes do not return 'file&#x
[
https://issues.apache.org/jira/browse/LOG4PHP-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reassigned LOG4PHP-194:
Assignee: Ivan Habunek
> replace xdoc/apt with something nor
[
https://issues.apache.org/jira/browse/LOG4PHP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-208.
--
Resolution: Duplicate
Assignee: Ivan Habunek
Brian, MDC support for mongodb appender
[
https://issues.apache.org/jira/browse/LOG4PHP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848364#comment-13848364
]
Ivan Habunek commented on LOG4PHP-204:
--
Vladimir, this is in develop. Only too
[
https://issues.apache.org/jira/browse/LOG4PHP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reassigned LOG4PHP-204:
Assignee: Ivan Habunek
> MDC context information in mongo appen
[
https://issues.apache.org/jira/browse/LOG4PHP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-204.
--
Resolution: Fixed
Fix Version/s: develop
> MDC context information in mongo appen
, Christian Grobmeier wrote:
> On 1 Dec 2013, at 11:37, Ivan Habunek wrote:
>
>> On 1 December 2013 11:23, Christian Grobmeier wrote:
>>>
>>> In Log4j2 we have not kept it because we lack of such a scenario. In
>>> addition people
>>> seem to be confus
st-commit-hook installed that triggers
> detection of "packagist.org").
>
> Regards,
> Sven
>
>> Ivan Habunek hat am 1. Dezember 2013 um 12:41
>> geschrieben:
>>
>>
>> I'd like to start the release procedure for 2.3.1 next week. Does
>>
12:47, Ivan Habunek wrote:
> Good news everybody! (tm)
>
> I invested some time and implemented namespaces in log4php. The new
> branch is called "v3". Please feel free to check it out and give
> feedback.
>
> Classes have been renamed to more sensible
Good news everybody! (tm)
I invested some time and implemented namespaces in log4php. The new
branch is called "v3". Please feel free to check it out and give
feedback.
Classes have been renamed to more sensible names for a namespaced
project. So LoggerAppenderConsole is now
Apache\Log4php\Append
I'd like to start the release procedure for 2.3.1 next week. Does
anybody have something which they really want in 2.3.1? Please hold of
any non-critical changes if possible. We need this release to
establish a new release procedure, with a new web site and moving docs
to Sphinx (see "docs" branch
[
https://issues.apache.org/jira/browse/LOG4PHP-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-166.
> LoggerAppenderMongoDB should supply a timeout value to the Mongo()
> constructor when it co
[
https://issues.apache.org/jira/browse/LOG4PHP-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-175.
> Change layout in default configuration to LoggerLayoutSim
[
https://issues.apache.org/jira/browse/LOG4PHP-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-168.
> Passing an instance of a configurator class to the Logger::configure function
> gives an
[
https://issues.apache.org/jira/browse/LOG4PHP-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-180.
> Remove $_ENV and $_SERVER access from Logger
[
https://issues.apache.org/jira/browse/LOG4PHP-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-167.
> INI configuration files not parse when using PHP 5.
[
https://issues.apache.org/jira/browse/LOG4PHP-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-172.
> Add more conversion words to the pattern layout and allow longer conversion
>
On 1 December 2013 11:23, Christian Grobmeier wrote:
> In Log4j2 we have not kept it because we lack of such a scenario. In
> addition people
> seem to be confused over NDC. Curious about your ideas here (also useful for
> docs, in case we keep it).
Consider a scenario where you have a layered ap
on working on 3.0 release. But can support 2.x version too.
> Can i read about log4php development and release flow somewhere?
>
>
> 2013/11/30 Ivan Habunek
>>
>> We actually have MDC and NDC.
>>
>> https://github.com/apache/logging-log4php/blob/master/src/main
On 30 November 2013 21:23, Christian Grobmeier wrote:
>> We actually have MDC and NDC.
>>
> Thanks. I know remember that I put some work in these classes before ages.
>
> In this case I am caring about the docs.
>
> However I never found much sense in the NDC. Any objections to remove NDC?
I neve
it is the thread context:
> http://logging.apache.org/log4j/2.x/manual/thread-context.html
>
> I really see benefits in having such a feature in log4php as well. not sure
> how to start with, but I would love
> to see it in 3.0.
>
> Cheers
>
>
> On 26 Nov 2013, at 11:2
[
https://issues.apache.org/jira/browse/LOG4PHP-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-212.
--
Resolution: Fixed
Assignee: Ivan Habunek
Removed old 2.2.1 release. Only the latest
possible
> for my own integration of Log4php. ;)
>
>
>
>
> Ivan Habunek schrieb:
>>
>> Hi Sven, nice to have you aboard.
>>
>> I don't thing it's a good idea to release a final 3.0 version which
>> will change a lot in future versions. And if we just tack o
change the internal levels, too.
>
> 5. Release 3.0. ;)
>
> 6. Only now think about features helping with PSR-3.
>
> This shouldn't take very much time. I'd try to help where I can, but point 1
> is keeping me from having done the rest as a pull request already.
>
Hi everyone, it's been a while...
Dmitriy Ulyanov contacted me and said he's interested in continuing
work on log4php. I'd like to continue the discussion here on the
mailing list.
So, Dmitriy, what approach did you have in mind? For starters, did you
plan on working on 3.0 release (a rewrite whi
On 7 June 2013 20:29, Christian Grobmeier wrote:
> Also I found out one needs to give a full path to the rolling file.
> Like /var/www/xyz.log.
> Otherwise filesize() would return with a warning. We could disable
> that warning with @filesize, but i am not sure if that is a good idea.
>
> Here is
On 7 June 2013 20:29, Christian Grobmeier wrote:
> Hi,
>
> these docs:
> http://logging.apache.org/log4php/docs/appenders/rolling-file.html
>
> say, one must include a %s:
> "Should contain a %s which gets substituted by the date."
>
> I have tried that, but it seems I don't need to do that. From
In Berlin. Will respond next week. :)
Ivan
On 29 May 2013 10:19, Christian Grobmeier wrote:
> I think Ivan has started some effort here.
> Actually I believe we need to go with namespaces soon.
>
> On Thu, May 16, 2013 at 5:23 PM, Florian Semm wrote:
> > Hey,
> >
> > are there any plans to ad
[
https://issues.apache.org/jira/browse/LOG4PHP-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639124#comment-13639124
]
Ivan Habunek commented on LOG4PHP-188:
--
Frankly, the logger hierarchy does not
[
https://issues.apache.org/jira/browse/LOG4PHP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-207.
Resolution: Fixed
Fix Version/s: 2.3.0
Assignee: Ivan Habunek
Applied patch
On 28 February 2013 20:34, Palmer, Eric wrote:
> I finally got permission from our attorney and have submitted the ICLA.
> Let me know when you get notified and I will begin to work on the
> appender for amazon cloud Simple Notification Services and
> then the SimpleDB appender.
Good news. Will d
On 17 January 2013 07:47, Florian Semm wrote:
> Somebody should become a member of the fig voters board.
I went ahead and nominated myself:
https://groups.google.com/d/topic/php-fig/meAfHFOk10M/discussion
Let's see how that goes.
Regards,
Ivan
On 17 January 2013 21:53, Christian Grobmeier wrote:
> There will be a day we need to support namespaces. PHP is progressing
> and namespaces are part of it.
> Maybe we should put the non-namespace code to maintenance mode and
> start with namespacing in newer versions
Yeah I agree, but I wanted
On 17 January 2013 07:47, Florian Semm wrote:
> The fingerprint and naming of all logging methods is quite different to the
> methods of log4php. It means much adjustments in the Logger class. Maybe a
> wrapper class, which implements the LoggerInterface, would be helpful.
I think a wrapper is
[
https://issues.apache.org/jira/browse/LOG4PHP-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554361#comment-13554361
]
Ivan Habunek commented on LOG4PHP-205:
--
I never encountered this. Do you have
On 15 January 2013 21:22, Florian Semm wrote:
> Are there any considerations about a implementation of the the new PSR-3
> standard in log4php?
Hm, that's very interesting. Didn't realise that FIG put out a new
standard, and for logging, no less!
Thanks for pointing this out. I'll definitely ch
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-200.
Resolution: Fixed
Fix Version/s: 3.0.0
Assignee: Ivan Habunek
Code is in develop
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545946#comment-13545946
]
Ivan Habunek commented on LOG4PHP-200:
--
I pushed the changes into branch n
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545887#comment-13545887
]
Ivan Habunek commented on LOG4PHP-200:
--
But then you would have to d
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13545873#comment-13545873
]
Ivan Habunek commented on LOG4PHP-200:
--
Finally I have managed to reproduce
On 6 January 2013 19:50, Palmer, Eric wrote:
> LoggerAppenderAwsSQS
> LoggerAppenderAwsSNS
> LoggerAppenderAwsSimpleDB
>
> What is your preference
I'd prefer the second variation - the one with capitalised SQS and
SNS. Looks better to me.
Currently, the component naming is not very well defined.
Hi Eric,
Glad to have you on board!
I'm currently in the process of writing some git guidelines. We
migrated from SVN just very recently. Hope to have that finished soon,
so you'll have some reference.
Regarding unit tests, what would be the requirements for running some
tests which actually log
Hi Dmitriy,
I have discussed your contribution with the Apache legal department
considering the licensing terms.
Since it's a relatively big contribution, it would be best if you
would be willing to sign the Apache Individual Contributor License
Agreement [1]. Please read the text. If you underst
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-203.
Assignee: Ivan Habunek
Good work. Applied. Closing issue.
> Capped collecti
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek updated LOG4PHP-203:
-
Fix Version/s: (was: develop)
3.0.0
> Capped collections support
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541614#comment-13541614
]
Ivan Habunek commented on LOG4PHP-203:
--
Interesting that it was producing diffe
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541385#comment-13541385
]
Ivan Habunek commented on LOG4PHP-203:
--
Good! I'm off for this year. See
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541380#comment-13541380
]
Ivan Habunek commented on LOG4PHP-203:
--
The same under Windows 7 64bit + Mon
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541357#comment-13541357
]
Ivan Habunek commented on LOG4PHP-203:
--
I have tests failing with MongoDB vers
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541342#comment-13541342
]
Ivan Habunek commented on LOG4PHP-203:
--
Also, wrap messages to 74 chars (or
[
https://issues.apache.org/jira/browse/LOG4PHP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541339#comment-13541339
]
Ivan Habunek commented on LOG4PHP-203:
--
Cool.
In future, could you use &quo
[
https://issues.apache.org/jira/browse/LOG4PHP-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-197.
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
develop
[
https://issues.apache.org/jira/browse/LOG4PHP-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-144.
Resolution: Fixed
Assignee: Ivan Habunek
Fixed this, also improved code to check mandatory
[
https://issues.apache.org/jira/browse/LOG4PHP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-201.
Resolution: Fixed
Assignee: Ivan Habunek
Patch applied. I can confirm that tests now pass
[
https://issues.apache.org/jira/browse/LOG4PHP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek updated LOG4PHP-201:
-
Component/s: Tests
> Tests are not passing
> -
>
>
[
https://issues.apache.org/jira/browse/LOG4PHP-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540880#comment-13540880
]
Ivan Habunek commented on LOG4PHP-125:
--
I don't see why not. If you upd
[
https://issues.apache.org/jira/browse/LOG4PHP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540868#comment-13540868
]
Ivan Habunek commented on LOG4PHP-69:
-
Have at it!
I would just advise that we d
[
https://issues.apache.org/jira/browse/LOG4PHP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540857#comment-13540857
]
Ivan Habunek commented on LOG4PHP-201:
--
You probably don't have the permis
[
https://issues.apache.org/jira/browse/LOG4PHP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540854#comment-13540854
]
Ivan Habunek commented on LOG4PHP-202:
--
Repo access fixed in wiki. I'll l
[
https://issues.apache.org/jira/browse/LOG4PHP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540844#comment-13540844
]
Ivan Habunek commented on LOG4PHP-202:
--
I agree fully. I wanted to wait a li
[
https://issues.apache.org/jira/browse/LOG4PHP-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539318#comment-13539318
]
Ivan Habunek commented on LOG4PHP-201:
--
I can reproduce this issue on Ubuntu.
Hi Dmitriy,
Thanks again for your contribution.
I'm talking to people at legal to check about the GPL license issue.
So I wanted to ask:
1. Is this code 100% yours or does it include anything written by others?
2. Would you be willing to donate the code to ASF under the terms of
the Apache Licens
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535994#comment-13535994
]
Ivan Habunek commented on LOG4PHP-200:
--
Hm, I'm unable to reproduce it o
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535962#comment-13535962
]
Ivan Habunek edited comment on LOG4PHP-200 at 12/19/12 1:5
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535965#comment-13535965
]
Ivan Habunek commented on LOG4PHP-200:
--
OK, I see you added the code.
[
https://issues.apache.org/jira/browse/LOG4PHP-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535962#comment-13535962
]
Ivan Habunek commented on LOG4PHP-200:
--
Sorry, I must have missed your e
[
https://issues.apache.org/jira/browse/LOG4PHP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reassigned LOG4PHP-193:
Assignee: Ivan Habunek
> Separate the web and the user'
[
https://issues.apache.org/jira/browse/LOG4PHP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534030#comment-13534030
]
Ivan Habunek commented on LOG4PHP-193:
--
I have commited the initial implementa
Ivan Habunek created LOG4PHP-199:
Summary: LoggerFilterLevelRange behaviour inconsistent with docs
Key: LOG4PHP-199
URL: https://issues.apache.org/jira/browse/LOG4PHP-199
Project: Log4php
[
https://issues.apache.org/jira/browse/LOG4PHP-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-83.
---
Resolution: Won't Fix
Since properties configuration format has been deprecated for a while
[
https://issues.apache.org/jira/browse/LOG4PHP-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reopened LOG4PHP-198:
--
Reopening to change resolution.
> Undefined property: LoggerFormattingI
[
https://issues.apache.org/jira/browse/LOG4PHP-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-198.
Resolution: Cannot Reproduce
> Undefined property: LoggerFormattingInfo::$leftAl
[
https://issues.apache.org/jira/browse/LOG4PHP-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530270#comment-13530270
]
Ivan Habunek commented on LOG4PHP-198:
--
I'm not familiar with Magento s
[
https://issues.apache.org/jira/browse/LOG4PHP-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek closed LOG4PHP-191.
Resolution: Fixed
Fix Version/s: 2.3.0
Assignee: Ivan Habunek
Install
>
>
> On Fri, Nov 30, 2012 at 4:38 PM, Ivan Habunek wrote:
>> Heads up,
>>
>> If no problems are found by Monday (T+3) then I will notify infra to
>> continue with the migration process.
>>
>> Please take a little time to review the repo and r
Heads up,
If no problems are found by Monday (T+3) then I will notify infra to
continue with the migration process.
Please take a little time to review the repo and reply to the list if
you have any objections or remarks.
Regards,
Ivan
On 30 November 2012 08:09, Ivan Habunek wrote:
> Hi
Hi all,
I was notified by infra, that the log4php SVN repository is about to
switch to readonly mode so that migration to git can get started.
Once the migration is complete, we will start to operate on the new
git repository at:
https://git-wip-us.apache.org/repos/asf
I will post any news as th
Hi all,
I have submitted a ticket to move log4php to git. I believe this might
be a step in the right direction for attracting more submissions,
since I have encountered several people willing to contribute, but
reluctant with using svn.
The infra ticket is here:
https://issues.apache.org/jira/br
[
https://issues.apache.org/jira/browse/LOG4PHP-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484811#comment-13484811
]
Ivan Habunek commented on LOG4PHP-191:
--
Added composer.json to trunk and all
[
https://issues.apache.org/jira/browse/LOG4PHP-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484008#comment-13484008
]
Ivan Habunek commented on LOG4PHP-191:
--
Renamed all SVN tags from current fo
[
https://issues.apache.org/jira/browse/LOG4PHP-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek updated LOG4PHP-181:
-
Fix Version/s: (was: 2.3.0)
> The default configurator does not populate
[
https://issues.apache.org/jira/browse/LOG4PHP-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-172.
--
Resolution: Fixed
> Add more conversion words to the pattern layout and allow lon
[
https://issues.apache.org/jira/browse/LOG4PHP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek updated LOG4PHP-169:
-
Fix Version/s: (was: 2.3.0)
> all configuration examples should avaiable as PHP and
[
https://issues.apache.org/jira/browse/LOG4PHP-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek updated LOG4PHP-196:
-
Fix Version/s: (was: 2.3.0)
> Appender Rolling File: Seperate PHP processes attempt
1 - 100 of 470 matches
Mail list logo
