log4php-user@logging.apache.org Archives

Re: Configuration in PHP format

2013-03-14T10:27:40Z

On 14 March 2013 09:04, Gunnar Lindholm
 wrote:
> Yes, its acctually a simple case.
>
> I want to be able to load two different loggers
>
> $loggerFoo = Logger::getLogger('foo');
> $loggerBar = Logger::getLogger('bar');
>
> and they should write to different files.
>
> I have a file with rootLogger defined, but I'd like to define these two
> foo/bar loggers also.
>
> Any help would be greatly appreciated.
> Thank you.
>

Hi Gunnar,

Check out this config file:

First, there's 2 appenders, each logs to it's own file:
- appender "app1" logs to foo.log
- appender "app2" logs to bar.log

Then I set up 2 loggers:
- logger "logger1" is linked to appender "app1", and therefore will
log to foo.log
- logger "logger2" is linked to appender "app2", and therefore will
log to bar.log

Try it out by running something like:
Logger::getLogger('logger1')->info('this is logger1');
Logger::getLogger('logger2')->info('this is logger2');

Note that in this configuration the root logger is not linked to any
appender. Since loggers inherit appenders from the root logger, any
loggers apart from logger1 and logger2 will not log anything since
they have no appenders of their own, and no inherited appenders.

To fix that, configure the root logger to log somewhere (for example
file "baz.log"). Here's the new config:

It adds a new appender to log to baz.log and links it to the root logger.

Note that logger1 and logger2 will also inherit app3 from the root
logger, which means they will also log to baz.log, as well as their
own file (foo.log or bar.log). You can prevent that by turning off
their additivity, like this:

Try it out, let me know if it solves your problem or if you have any
further questions.

Regards,
Ivan

Re: Configuration in PHP format

2013-03-14T08:04:49Z

2013-03-13 21:52, Ivan Habunek skrev:
> On 13 March 2013 20:49, Gunnar Lindholm
>  wrote:
>> I wonder if you could add some more complex example of a configuration
>> made in PHP?
>>
>> It is not obvious how to write a configuration with loggers that you
>> give explicit names.
>
> I'm aware of that, and have been meaning to write up better examples
> but I haven't had much time recently to work on the project recently.
> Do you have something specific that you want to accomplish? Maybe I
> can help you there.


Hi.

Yes, its acctually a simple case.

I want to be able to load two different loggers

$loggerFoo = Logger::getLogger('foo');
$loggerBar = Logger::getLogger('bar');

and they should write to different files.

I have a file with rootLogger defined, but I'd like to define these two 
foo/bar loggers also.

Any help would be greatly appreciated.
Thank you.

Re: Configuration in PHP format

2013-03-13T20:52:10Z

On 13 March 2013 20:49, Gunnar Lindholm
 wrote:
> I wonder if you could add some more complex example of a configuration
> made in PHP?
>
> It is not obvious how to write a configuration with loggers that you
> give explicit names.

I'm aware of that, and have been meaning to write up better examples
but I haven't had much time recently to work on the project recently.
Do you have something specific that you want to accomplish? Maybe I
can help you there.

Regards,
Ivan

Configuration in PHP format

2013-03-13T19:49:20Z

Hi.

I wonder if you could add some more complex example of a configuration
made in PHP?

It is not obvious how to write a configuration with loggers that you
give explicit names.

Thanks in advance
Gunnar.

Re: custom file:line column entries

2013-03-07T07:23:02Z

On 5 March 2013 19:05, David Coombes  wrote:
> I have a method in a class that calls Logger::info() The issue is the
> file:line column in the html appender will always report my helper method
> and not the calling file:line. Using php's debug_backtrace I can get the
> calling file:line but can't see how I can dynamically change the column. Is
> this possible, or is there a Logger::method() that I need to overwrite?

Hi!

Currently it's not possible to override the location information.
There is a hackish way of doing this, but you have to modify log4php
code.

Add this method to LoggerLoggingEvent class (located in /src/main/php/):
public function setLocationInformation(LoggerLocationInfo $locationInfo) {
    $this->locationInfo = $locationInfo;
}

And then do this:

public function log($msg, $level = "info")
{
    // Manually construct a logging event
    $level = LoggerLevel::toLevel($level);
    $logger = Logger::getLogger(__CLASS__);
    $event = new LoggerLoggingEvent(__CLASS__, $logger, $level, $msg);

    // Override the location info
    $bt = debug_backtrace();
    $caller = array_shift($bt);
    $location = new LoggerLocationInfo($caller);
    $event->setLocationInformation($location);

    // Log it
    $logger->logEvent($event);
}

Just tried it out. Seems to work fine. Let me know how it works.

I will add LoggerLoggingEvent::setLocationInformation() to the develop
branch so it will be included in next release.

Looking at the HTML layout... man, it's really outdated. Still has
Category instead of Logger, and other stuff... Will have to update it.
:)

Best regards,
Ivan

custom file:line column entries

2013-03-05T18:05:33Z

HI,

I have a method in a class that calls Logger::info() The issue is the
file:line column in the html appender will always report my helper method
and not the calling file:line. Using php's debug_backtrace I can get the
calling file:line but can't see how I can dynamically change the column. Is
this possible, or is there a Logger::method() that I need to overwrite?

My helper method currently is:
public function log( $msg, $level='info' ){
//trace
$bt = debug_backtrace();
$caller = array_shift($bt);
$trace = $caller['file'] . ":" . $caller['line'];
$this->log_api->trace($trace);
 //log
$this->log_api->$level( $msg );
}
}

And my xml config is:








regards,
Daithi

-- 
"Any society that would give up a little liberty to gain a little security,
               will deserve neither and lose both." *- Benjamin Franklin*

Re: Two appenders

2013-02-19T20:36:22Z

On 19 February 2013 21:23, Jan Galler  wrote:
> Hi everyone,

Hi Jan!

> I'm trying to create a logger that covers two outputs. The first one is
> a database (so every stuff should go there). And now I try to add an
> appender that sends every log-event with an level higher 'warn'.
>
> But I really don't get it working?! I'm doing the following code (PHP):
>
> --snip--
>

Under 'appenders' you have an array with two identical keys, basically
you do this:

'appenders' => array(
    'default' => ...,
    'default' => ...,
)

So the second one overrides the first. You should name them
differently, e.g. 'dbappender' and 'emailappender' (or whatever else
you like).

Finally, to link both appenders to the root logger, do this:

'rootLogger' => array(
    'appenders' => array('dbappender', 'emailappender'),
),

Also, you don't need to use filters in this case, just set the
appender threshold to 'warn' and it will filter out levels under
'warn'. To do this, replace 'filters' with:
'threshold' => 'warn'

Here's the whole shebang:

Logger::configure(
    array(
        'appenders' => array(
            'dbappender' => array(
                'class' => 'LoggerAppenderPDO',
                'params' => array(
                    'dsn' =>
'mysql:host='.$logHost.';port='.$logPort.';dbname='.$logName,
                    'user' => $logUser,
                    'password' => $logPass,
                    'table' => 'log4php_log',
                ),
            ),
            'emailappender' => array(
                'class' => 'LoggerAppenderMailEvent',
                'layout' => array(
                    'class' => 'LoggerLayoutSimple',
                ),
                'params' => array(
                    'to' => 'jagaller@icloud.com',
                    'from' => 'logger@asdf.com'
                ),
                'threshold' => 'warn'
            ),
        ),
        'rootLogger' => array(
            'appenders' => array('dbappender', 'emailappender'),
        )
    )
);


Try it out and see if it works. ;)

Regards,
Ivan

Two appenders

2013-02-19T20:23:17Z

Hi everyone,

I'm trying to create a logger that covers two outputs. The first one is 
a database (so every stuff should go there). And now I try to add an 
appender that sends every log-event with an level higher 'warn'.

But I really don't get it working?! I'm doing the following code (PHP):

Logger::configure(
	array(
	    'appenders' =3D> array(
	        'default' =3D> array(
	            'class' =3D> 'LoggerAppenderPDO',
	            'params' =3D> array(
	                'dsn' =3D> =
'mysql:host=3D'.$logHost.';port=3D'.$logPort.';dbname=3D'.$logName,
	                'user' =3D> $logUser,
	                'password' =3D> $logPass,
	                'table' =3D> 'log4php_log',
	            ),
	         'default' =3D> array(
	             'class' =3D> 'LoggerAppenderMailEvent',
	             'layout' =3D> array(
	                 'class' =3D> 'LoggerLayoutSimple',
	             ),
	             'params' =3D> array(
	                 'to' =3D> 'jagaller@icloud.com',
	                 'from' =3D> 'logger@asdf.com'
	             ),
	             'filters' =3D> array(
	             	array(
	             		'class' =3D> 'LoggerFilterLevelRange',
	                     'params' =3D> array(
	                     	'levelMin' =3D> 'warn',
	                         'levelMax' =3D> 'error',
	                     )
	             	)
	         	)
	         ),
	           =20
	        ),
	    ),
	    'rootLogger' =3D> array(
	        'appenders' =3D> array('default'),
	    ),

	)
);


Can anyone advise me how to do that?



Best regards,
Jan Galler

Re: File logging is working but not Console logging!

2013-01-23T12:48:14Z

On 23 January 2013 13:43, James Pittman  wrote:
> Interesting.  If you do just
> print "Hello World";
>
> It will print to console and browser - I just assumed that was stdout.

Print and echo actually write to php://output stream, and not
php://stdout. Frankly, I'm not sure exactly what happens under the
hood, just what it says in the manual. Maybe someone else on the list
can explain it better.

Regards,
Ivan

Re: File logging is working but not Console logging!

2013-01-23T12:43:01Z

On Wed, Jan 23, 2013 at 2:25 AM, Ivan Habunek wrote:

> On 23 January 2013 03:52, James Pittman  wrote:
> > Yes that was it.  I was trying to output it to a browser.  I shouldn't
> have
> > said "console stdout" - I just assumed that if it would output to a
> console,
> > it would output to a browser... but it must check to see whether you're
> in a
> > browser or CLI.
>
> Well not exactly, the appender makes no checks. It's just that writing
> directly to stdout will not output anything to the browser when using
> apache.
>
> Check out this link:
> http://stackoverflow.com/questions/11318768/php-stdout-on-apache
>

Interesting.  If you do just
print "Hello World";

It will print to console and browser - I just assumed that was stdout.

Jamie

Re: File logging is working but not Console logging!

2013-01-23T07:25:09Z

On 23 January 2013 03:52, James Pittman  wrote:
> Yes that was it.  I was trying to output it to a browser.  I shouldn't have
> said "console stdout" - I just assumed that if it would output to a console,
> it would output to a browser... but it must check to see whether you're in a
> browser or CLI.

Well not exactly, the appender makes no checks. It's just that writing
directly to stdout will not output anything to the browser when using
apache.

Check out this link:
http://stackoverflow.com/questions/11318768/php-stdout-on-apache

Regards,
Ivan

Re: File logging is working but not Console logging!

2013-01-23T02:52:23Z

On Tue, Jan 22, 2013 at 4:44 PM, Ivan Habunek wrote:

> On 22 January 2013 22:36, James Pittman  wrote:
> > OK I fixed that, but I'm still not getting any console stdout.
>
> That's strange. Works for me...
> http://i.imgur.com/22BB8Ly.png
>
> Note that the console appender output will not be seen in browser,
> only via CLI. Just noticed this is not in the docs. :) In that case
> you have to use LoggerAppenderEcho.
>
> Does this help? If not, which version of php and log4php are you using?
>

Yes that was it.  I was trying to output it to a browser.  I shouldn't have
said "console stdout" - I just assumed that if it would output to a
console, it would output to a browser... but it must check to see whether
you're in a browser or CLI.

Thanks!

Jamie

Re: File logging is working but not Console logging!

2013-01-22T21:44:04Z

On 22 January 2013 22:36, James Pittman  wrote:
> OK I fixed that, but I'm still not getting any console stdout.

That's strange. Works for me...
http://i.imgur.com/22BB8Ly.png

Note that the console appender output will not be seen in browser,
only via CLI. Just noticed this is not in the docs. :) In that case
you have to use LoggerAppenderEcho.

Does this help? If not, which version of php and log4php are you using?

Regards,
Ivan

Re: File logging is working but not Console logging!

2013-01-22T21:36:25Z

On Tue, Jan 22, 2013 at 4:32 PM, Ivan Habunek wrote:

> On 22 January 2013 22:26, James Pittman  wrote:
> > Using the examples in the instructions, I created a config file and PHP
> > file.  I am getting the expected logging in the myLog.log, but nothing
> in my
> > STDOUT.  If I do NOT include the config.xml file, I DO get logging in
> > STDOUT.  Any ideas?
>
> Yes!
>
> s/looger/logger/
>
> You misspelled  in your config file. :)
>
> Regards!
> Ivan
>

LOL!

OK I fixed that, but I'm still not getting any console stdout.

Jamie

Re: File logging is working but not Console logging!

2013-01-22T21:32:38Z

On 22 January 2013 22:26, James Pittman  wrote:
> Using the examples in the instructions, I created a config file and PHP
> file.  I am getting the expected logging in the myLog.log, but nothing in my
> STDOUT.  If I do NOT include the config.xml file, I DO get logging in
> STDOUT.  Any ideas?

Yes!

s/looger/logger/

You misspelled  in your config file. :)

Regards!
Ivan

File logging is working but not Console logging!

2013-01-22T21:26:01Z

Using the examples in the instructions, I created a config file and PHP
file.  I am getting the expected logging in the myLog.log, but nothing in
my STDOUT.  If I do NOT include the config.xml file, I DO get logging in
STDOUT.  Any ideas?


XML file:



    
        
        
        
    
    
    
        
    
    
        
        
    



My PHP file:
info("Logging from main.");

/**
 * This is a classic usage pattern: one logger object per class.
 */
class Foo {

    /** Holds the Logger. */
    private $log;

    /** Logger is instantiated in the constructor. */
    public function __construct() {
// The __CLASS__ constant holds the class name, in our case "Foo".
// Therefore this creates a logger named "Foo" (which we configured in the
config file)
        $this->log = Logger::getLogger(__CLASS__);
    }

    /** Logger can be used from any member method. */
    public function go() {
        $this->log->info("Logging from Foo.");
    }

}

$foo = new Foo();
$foo->go();
?>




-- 
____________________________________________________________________________________
Taste and see the fullness of His peace, and hold on to what's being held
out.
~ from "The Healing Hand of God" by Matthew West

Log4php git repository is live

2012-12-08T11:26:07Z

Hi all,

Thanks to Gavin from Infra, our git repository is live as of today.
This marks the end of svn for log4php code. The svn repo will remain
available in read-only mode.

Here's the links you might need:

The official repository (and web interface), writable for developers:
https://git-wip-us.apache.org/repos/asf/logging-log4php.git

Official read-only mirror:
git://git.apache.org/logging-log4php.git

Github read-only mirror:
https://github.com/apache/logging-log4php

Note that the old apache and github mirrors, which were named
"log4php.git" instead of the current name "logging-log4php.git" will
be removed at some point in time, so don't use those for anything.

The github mirror is updated once daily. I was told that it's not
possible to update on commit since it's a mirror of the git.apache.org
mirror, and not of the main repository. I will look into possible ways
of improving this.

None of the other Logging Services projects are affected by this
change, except in a way to encourage them to move to git at some point
in time. The transition was very painless.

Best regards,
Ivan

Re: Verifying the git repo

2012-12-02T16:23:13Z

Regarding git branching model, I read these two howtos:


http://nvie.com/posts/a-successful-git-branching-model/

This document is pretty much thought out, and I guess it really covers the
development/release processes of log4php. I would use it as a reference.
Since now, I was
using lightweight tags, but document recommends using annotated tags with
-a option. For this kind of project that log4php is, annotated tags are
more suitable.
So +1 from me, for this model.


https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/

Even though, the first document doesn't cover too much, there is really
interesting passage about rebasing multiple commits.




On Sun, Dec 2, 2012 at 4:58 PM, Ivan Habunek  wrote:

> On 30 November 2012 17:07, Vladimír Gorej  wrote:
> > I did not find any problems with the repo, except already known problem
> with
> > the duplicate tags. I reviewed some of the history commits with 'git gui'
> > tool and everything seemed fine.
>
> Yeah, i did the same using tortoise-git, and all seems well.
>
> > Maybe we should have a look at this:
> > https://help.github.com/articles/dealing-with-line-endings#platform-all,
> if
> > commiters/contributors develop on various platforms.
>
> Well, the plan was to start using PSR-2 coding standard, and it says
> that all files should use unix-style line breaks (LF) regardless of
> the platform.
>
> So the simplest solution is to put the following line in .gitattributes:
> * text eol=lf
>
> That way all line breaks will be converted to LF.
>
> Regards,
> Ivan
>



-- 

Vladimír Gorej | CodeScale s.r.o.
email: gorej@codescale.net
tel: +420 777 861 279, +421 948 023 011
web: http://www.codescale.net

Re: Verifying the git repo

2012-12-02T15:58:03Z

On 30 November 2012 17:07, Vladimír Gorej  wrote:
> I did not find any problems with the repo, except already known problem with
> the duplicate tags. I reviewed some of the history commits with 'git gui'
> tool and everything seemed fine.

Yeah, i did the same using tortoise-git, and all seems well.

> Maybe we should have a look at this:
> https://help.github.com/articles/dealing-with-line-endings#platform-all, if
> commiters/contributors develop on various platforms.

Well, the plan was to start using PSR-2 coding standard, and it says
that all files should use unix-style line breaks (LF) regardless of
the platform.

So the simplest solution is to put the following line in .gitattributes:
* text eol=lf

That way all line breaks will be converted to LF.

Regards,
Ivan

Re: Verifying the git repo

2012-11-30T16:07:29Z

+1

I did not find any problems with the repo, except already known problem
with the duplicate tags. I reviewed some of the history commits with 'git
gui' tool and everything seemed fine.
Maybe we should have a look at this:
https://help.github.com/articles/dealing-with-line-endings#platform-all, if
commiters/contributors develop on various platforms.


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 reply to the list if
> you have any objections or remarks.
>
> Regards,
> Ivan
>
> On 30 November 2012 08:09, Ivan Habunek  wrote:
> > Hi all,
> >
> > The new git repository is set up and located at:
> > https://git-wip-us.apache.org/repos/asf/logging-log4php.git
> >
> > Quoting:
> > "It is the responsibility of each project to review the Git history in
> > their new repository before it is made the official repository. In the
> > event that a project has to revert to SVN due to a bad Git clone, it
> > is the project's responsibility to reapply writes made to Git back to
> > SVN. It is in the project's best interest to make sure that the
> > history is correct before starting to use it as an official
> > repository."
> > -- from https://git-wip-us.apache.org/docs/switching-to-git.html
> >
> > I will try to verify everything is good, but I would appreciate extra
> > sets of eyes on this one! So clone and compare with svn if you have
> > the time, and report any issues here. Thanks!
> >
> > There is one known issue, since we renamed our tags to be compatible
> > with Composer, they seem to appear twice for each released version.
> > E.g. both old style: "apache-log4php-2.3.0" and new: "2.3.0". This
> > should not present a problem, we'll just delete the old tag style
> > after migration is final.
> >
> > Regards,
> > Ivan
>



-- 

Vladimír Gorej | CodeScale s.r.o.
email: gorej@codescale.net
tel: +420 777 861 279, +421 948 023 011
web: http://www.codescale.net

Re: Verifying the git repo

2012-11-30T15:38:36Z

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 all,
>
> The new git repository is set up and located at:
> https://git-wip-us.apache.org/repos/asf/logging-log4php.git
>
> Quoting:
> "It is the responsibility of each project to review the Git history in
> their new repository before it is made the official repository. In the
> event that a project has to revert to SVN due to a bad Git clone, it
> is the project's responsibility to reapply writes made to Git back to
> SVN. It is in the project's best interest to make sure that the
> history is correct before starting to use it as an official
> repository."
> -- from https://git-wip-us.apache.org/docs/switching-to-git.html
>
> I will try to verify everything is good, but I would appreciate extra
> sets of eyes on this one! So clone and compare with svn if you have
> the time, and report any issues here. Thanks!
>
> There is one known issue, since we renamed our tags to be compatible
> with Composer, they seem to appear twice for each released version.
> E.g. both old style: "apache-log4php-2.3.0" and new: "2.3.0". This
> should not present a problem, we'll just delete the old tag style
> after migration is final.
>
> Regards,
> Ivan

Verifying the git repo

2012-11-30T07:09:25Z

Hi all,

The new git repository is set up and located at:
https://git-wip-us.apache.org/repos/asf/logging-log4php.git

Quoting:
"It is the responsibility of each project to review the Git history in
their new repository before it is made the official repository. In the
event that a project has to revert to SVN due to a bad Git clone, it
is the project's responsibility to reapply writes made to Git back to
SVN. It is in the project's best interest to make sure that the
history is correct before starting to use it as an official
repository."
-- from https://git-wip-us.apache.org/docs/switching-to-git.html

I will try to verify everything is good, but I would appreciate extra
sets of eyes on this one! So clone and compare with svn if you have
the time, and report any issues here. Thanks!

There is one known issue, since we renamed our tags to be compatible
with Composer, they seem to appear twice for each released version.
E.g. both old style: "apache-log4php-2.3.0" and new: "2.3.0". This
should not present a problem, we'll just delete the old tag style
after migration is final.

Regards,
Ivan

Re: SVN going to readonly mode

2012-11-28T21:51:59Z

On Wed, Nov 28, 2012 at 8:52 PM, Vladimír Gorej  wrote:
> Sure, if it is on git, I will be as active as I can. Btw I have been working
> with git for 2 years now, so if anybody have a problem or a question
> regarding git, I will be more than happy to help.

Good to know!

>
>
> On Wed, Nov 28, 2012 at 8:43 PM, Ivan Habunek 
> wrote:
>>
>> On 28 November 2012 19:55, Vladimír Gorej  wrote:
>> > We are very glad to hear that ;] Thanks a lot.
>>
>> Hey, I hope you will be on-board for the push towards v3.0.
>>
>> Regards,
>> Ivan
>
>
>
>
> --
>
> Vladimír Gorej | CodeScale s.r.o.
> email: gorej@codescale.net
> tel: +420 777 861 279, +421 948 023 011
> web: http://www.codescale.net
>
>



--
http://www.grobmeier.de
https://www.timeandbill.de

Re: SVN going to readonly mode

2012-11-28T20:08:35Z

On 28 November 2012 20:52, Vladimír Gorej  wrote:
> Sure, if it is on git, I will be as active as I can. Btw I have been working
> with git for 2 years now, so if anybody have a problem or a question
> regarding git, I will be more than happy to help.

That's great. We'll discuss the workflow in more detail soon. I have
some ideas, and could use some feedback.

Ivan

Re: SVN going to readonly mode

2012-11-28T19:52:47Z

Sure, if it is on git, I will be as active as I can. Btw I have been
working with git for 2 years now, so if anybody have a problem or a
question regarding git, I will be more than happy to help.

On Wed, Nov 28, 2012 at 8:43 PM, Ivan Habunek wrote:

> On 28 November 2012 19:55, Vladimír Gorej  wrote:
> > We are very glad to hear that ;] Thanks a lot.
>
> Hey, I hope you will be on-board for the push towards v3.0.
>
> Regards,
> Ivan
>

-- 

Vladimír Gorej | CodeScale s.r.o.
email: gorej@codescale.net
tel: +420 777 861 279, +421 948 023 011
web: http://www.codescale.net

Re: SVN going to readonly mode

2012-11-28T19:43:09Z

On 28 November 2012 19:55, Vladimír Gorej  wrote:
> We are very glad to hear that ;] Thanks a lot.

Hey, I hope you will be on-board for the push towards v3.0.

Regards,
Ivan

Apache Logging Services IRC channel

2012-11-28T19:40:57Z

I just registered #asflogging channel on irc.freenode.net. Everyone's
welcome for any logging related discussions, including all
subprojects, or just for hanging out.

Please come join me so I won't be all alone. :)

Regards,
Ivan

Re: SVN going to readonly mode

2012-11-28T18:55:37Z

We are very glad to hear that ;] Thanks a lot.


On Wed, Nov 28, 2012 at 7:29 PM, Ivan Habunek wrote:

> 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 they come in.
>
> Regards,
> Ivan
>



-- 

Vladimír Gorej | CodeScale s.r.o.
email: gorej@codescale.net
tel: +420 777 861 279, +421 948 023 011
web: http://www.codescale.net

SVN going to readonly mode

2012-11-28T18:29:11Z

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 they come in.

Regards,
Ivan

RE: Moving log4php to git

2012-11-12T13:55:50Z

I know the differences as I did an analysis recently for work but on second thought an opensource
project like this may get more of a benefit from git than a private company might.

I use both so no biggy

-----Original Message-----
From: Christian Grobmeier [mailto:grobmeier@gmail.com] 
Sent: Monday, November 12, 2012 8:45 AM
To: Log4PHP User
Subject: Re: Moving log4php to git

On Mon, Nov 12, 2012 at 2:36 PM, Michael Sole  wrote:
> Yes I am aware, my point is that it would be counter intuitive. People would expect svn
use and while git it is the new golden child it doesn't really offer much more in the way
of advantages over svn. Moving repositories is a real pain.

Actually moving to git is straightforward. It works really well.
And there are many projects using git at Apache. Not all as first instance, but there are
some.
Look at: http://git.apache.org

That said we have had some requests of users who wanted to use git.
When it comes to the features svn/git: there actually are some differences. Personally I am
not religious on it, but it clearly see some benefits when it comes to mergin. In addition
we have received a couple of git patches so far.

> Just my opinion, though. I haven't contributed yet but I do use svn as my repo.

Well, look at it like me (i am not good with git): its a great chance to learn more about
it.

And hey... we are looking forward to your contributions :-)

Cheers

>
> -----Original Message-----
> From: Christian Grobmeier [mailto:grobmeier@gmail.com]
> Sent: Monday, November 12, 2012 8:34 AM
> To: Log4PHP User
> Subject: Re: Moving log4php to git
>
> On Mon, Nov 12, 2012 at 2:32 PM, Michael Sole  wrote:
>> And isn't log4php?
>
> It does not mean we are limited to ASF tools. Every project can freely 
> chose the tools it wants
>
>
>>
>> -----Original Message-----
>> From: Ivan Habunek [mailto:ivan.habunek@gmail.com]
>> Sent: Saturday, November 10, 2012 10:50 AM
>> To: Log4PHP User
>> Subject: Re: Moving log4php to git
>>
>> On 10 November 2012 16:47, Michael Sole  wrote:
>>> Isn't subversion an apache project?
>>
>> Yes it is. What's your point? :)
>>
>> Regards,
>> Ivan
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de

--
http://www.grobmeier.de
https://www.timeandbill.de

Re: Moving log4php to git

2012-11-12T13:46:11Z

On 12 November 2012 14:36, Michael Sole  wrote:
> Yes I am aware, my point is that it would be counter intuitive. People would expect svn
use and while git it is the new golden child it doesn't really offer much more in the way
of advantages over svn. Moving repositories is a real pain.
>
> Just my opinion, though. I haven't contributed yet but I do use svn as my repo.

There are several reasons for the switch.

Firstly, we developers agreed that we prefer working with git, so this
will make our jobs more pleasurable, and therefore more productive.

Secondly, there are a couple of contributors whose input I value who
said that they do not provide patches as often because we don't accept
git pull requests.

Also, I do not agree that git does not bring any significant
advantages. One simple example: try developing without an active
internet connection. I was in this position several times this year.

Apache infra project is managing the transition and they already have
a lot of experience doing this, so I don't anticipate many problems.

Regards,
Ivan

Re: Moving log4php to git

2012-11-12T13:44:41Z

On Mon, Nov 12, 2012 at 2:36 PM, Michael Sole  wrote:
> Yes I am aware, my point is that it would be counter intuitive. People would expect svn
use and while git it is the new golden child it doesn't really offer much more in the way
of advantages over svn. Moving repositories is a real pain.

Actually moving to git is straightforward. It works really well.
And there are many projects using git at Apache. Not all as first
instance, but there are some.
Look at: http://git.apache.org

That said we have had some requests of users who wanted to use git.
When it comes to the features svn/git: there actually are some
differences. Personally I am not religious on it, but it clearly see
some benefits when it comes to mergin. In addition we have received a
couple of git patches so far.

> Just my opinion, though. I haven't contributed yet but I do use svn as my repo.

Well, look at it like me (i am not good with git): its a great chance
to learn more about it.

And hey... we are looking forward to your contributions :-)

Cheers

>
> -----Original Message-----
> From: Christian Grobmeier [mailto:grobmeier@gmail.com]
> Sent: Monday, November 12, 2012 8:34 AM
> To: Log4PHP User
> Subject: Re: Moving log4php to git
>
> On Mon, Nov 12, 2012 at 2:32 PM, Michael Sole  wrote:
>> And isn't log4php?
>
> It does not mean we are limited to ASF tools. Every project can freely chose the tools
it wants
>
>
>>
>> -----Original Message-----
>> From: Ivan Habunek [mailto:ivan.habunek@gmail.com]
>> Sent: Saturday, November 10, 2012 10:50 AM
>> To: Log4PHP User
>> Subject: Re: Moving log4php to git
>>
>> On 10 November 2012 16:47, Michael Sole  wrote:
>>> Isn't subversion an apache project?
>>
>> Yes it is. What's your point? :)
>>
>> Regards,
>> Ivan
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de

--
http://www.grobmeier.de
https://www.timeandbill.de

RE: Moving log4php to git

2012-11-12T13:36:41Z

Yes I am aware, my point is that it would be counter intuitive. People would expect svn use
and while git it is the new golden child it doesn't really offer much more in the way of advantages
over svn. Moving repositories is a real pain.

Just my opinion, though. I haven't contributed yet but I do use svn as my repo.

-----Original Message-----
From: Christian Grobmeier [mailto:grobmeier@gmail.com] 
Sent: Monday, November 12, 2012 8:34 AM
To: Log4PHP User
Subject: Re: Moving log4php to git

On Mon, Nov 12, 2012 at 2:32 PM, Michael Sole  wrote:
> And isn't log4php?

It does not mean we are limited to ASF tools. Every project can freely chose the tools it
wants

>
> -----Original Message-----
> From: Ivan Habunek [mailto:ivan.habunek@gmail.com]
> Sent: Saturday, November 10, 2012 10:50 AM
> To: Log4PHP User
> Subject: Re: Moving log4php to git
>
> On 10 November 2012 16:47, Michael Sole  wrote:
>> Isn't subversion an apache project?
>
> Yes it is. What's your point? :)
>
> Regards,
> Ivan

--
http://www.grobmeier.de
https://www.timeandbill.de

Re: Moving log4php to git

2012-11-12T13:34:19Z

On Mon, Nov 12, 2012 at 2:32 PM, Michael Sole  wrote:
> And isn't log4php?

It does not mean we are limited to ASF tools. Every project can freely
chose the tools it wants


>
> -----Original Message-----
> From: Ivan Habunek [mailto:ivan.habunek@gmail.com]
> Sent: Saturday, November 10, 2012 10:50 AM
> To: Log4PHP User
> Subject: Re: Moving log4php to git
>
> On 10 November 2012 16:47, Michael Sole  wrote:
>> Isn't subversion an apache project?
>
> Yes it is. What's your point? :)
>
> Regards,
> Ivan



--
http://www.grobmeier.de
https://www.timeandbill.de

RE: Moving log4php to git

2012-11-12T13:32:03Z

And isn't log4php?

-----Original Message-----
From: Ivan Habunek [mailto:ivan.habunek@gmail.com] 
Sent: Saturday, November 10, 2012 10:50 AM
To: Log4PHP User
Subject: Re: Moving log4php to git

On 10 November 2012 16:47, Michael Sole  wrote:
> Isn't subversion an apache project?

Yes it is. What's your point? :)

Regards,
Ivan

Re: Moving log4php to git

2012-11-10T15:49:38Z

On 10 November 2012 16:47, Michael Sole  wrote:
> Isn't subversion an apache project?

Yes it is. What's your point? :)

Regards,
Ivan

Re: Moving log4php to git

2012-11-10T15:47:52Z

Isn't subversion an apache project?

Sent from my iPhone

On Nov 10, 2012, at 6:56 AM, "Florian Semm"  wrote:

> Am 09.11.2012 09:48, schrieb Ivan Habunek:
>> 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/browse/INFRA-5500
>> 
>> You will have prior notice before the change becomes final.
>> 
>> Best regards,
>> Ivan
> Hey,
> 
> thats greate +1
> 
> Florian

Re: Moving log4php to git

2012-11-10T11:55:43Z

Am 09.11.2012 09:48, schrieb Ivan Habunek:
> 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/browse/INFRA-5500
>
> You will have prior notice before the change becomes final.
>
> Best regards,
> Ivan
Hey,

thats greate +1

Florian

Moving log4php to git

2012-11-09T08:48:14Z

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/browse/INFRA-5500

You will have prior notice before the change becomes final.

Best regards,
Ivan

Re: Cannot find superglobal variable $_SERVER

2012-11-07T14:53:14Z

Ok, thank you for your help!

The information was already from phpinfo(). I have tried now also SEGPC 
but the effect was the same.

I have now an other file which makes same problem but not with $_SERVER 
rather with $_REQUEST. Again, if I use it once the warning disappears. 
I'm not sure but my impression was that in some script the variable is 
set and others not. Might depend on some circumstances that I don't 
know. But I'm also not a true php expert.

The site runs on 64bit Linux with PHP 5.4.8 but I don't know the Apache 
version.

Regards,
Robert

Am 07.11.2012 15:17, schrieb Ivan Habunek:
> On 7 November 2012 14:59, Robert Schneider  wrote:
>> Yes, variables_order is set to EGPCS. Could I savely change the order, in
>> hope that it might work then?
> Hm, I haven't come across this problem. Just did a quick test locally
> on windows/apache 2.2/php 5.4.8. My variables_order is set to GPCS by
> default. $_SERVER is populated correctly onCLI and on apache.
>
> What's your setup? Make sure you're looking at the right php.ini.
> Sometimes apache is configured to use a different php.inii file than
> the one used by CLI. It's best if you look at phpinfo() output
> instead.
>
> BTW, I'm at apachecon so I might not have enough time to investigate
> this. But I'm back home for the weekend.
>
> Regards,
> Ivan