Hi Logging Team,
The log4php pages still use Google Analytics(GA). I've created a PR against
the asf-site branch to remove it.
https://github.com/apache/logging-log4php-site/pull/2
It would be great if you could merge the PR
I'm not sure if any other old docs still have GA on
This vote has passed with 8 binding +1 votes. I will make the appropriate site
modifications and ask infra to lock down the issue tracker.
Ralph
My +1
Ralph
> On Dec 9, 2020, at 2:20 PM, Ralph Goers wrote:
>
> I started a discussion several days ago regarding moving Log4PHP to dormant
> status and have gotten no feedback. Given there has been no development
> activity in years and there is no one actively working on
; > Code base became very old and there is lots to do.
> >
> > --
> > The Apache Software Foundation
> > V.P., Data Privacy
> >
> > On Wed, Dec 9, 2020, at 22:20, Ralph Goers wrote:
> > > I started a discussion several days ago regarding m
acy
>
> On Wed, Dec 9, 2020, at 22:20, Ralph Goers wrote:
> > I started a discussion several days ago regarding moving Log4PHP to
> > dormant status and have gotten no feedback. Given there has been no
> > development activity in years and there is no one actively working on
&
Very sad, but +1.
Code base became very old and there is lots to do.
--
The Apache Software Foundation
V.P., Data Privacy
On Wed, Dec 9, 2020, at 22:20, Ralph Goers wrote:
> I started a discussion several days ago regarding moving Log4PHP to
> dormant status and have gotten no feedback.
+1
On Wed, Dec 9, 2020 at 10:20 PM Ralph Goers
wrote:
> I started a discussion several days ago regarding moving Log4PHP to
> dormant status and have gotten no feedback. Given there has been no
> development activity in years and there is no one actively working on the
> project
+1
On Thu, Dec 10, 2020 at 7:01 AM Matt Sicker wrote:
> +1
>
> On Wed, 9 Dec 2020 at 16:00, Gary Gregory wrote:
> >
> > +1
> >
> > Gary
> >
> > On Wed, Dec 9, 2020, 16:20 Ralph Goers
> wrote:
> >
> > > I started a discussion se
+1
On Wed, 9 Dec 2020 at 16:00, Gary Gregory wrote:
>
> +1
>
> Gary
>
> On Wed, Dec 9, 2020, 16:20 Ralph Goers wrote:
>
> > I started a discussion several days ago regarding moving Log4PHP to
> > dormant status and have gotten no feedback. Given there has be
+1
Gary
On Wed, Dec 9, 2020, 16:20 Ralph Goers wrote:
> I started a discussion several days ago regarding moving Log4PHP to
> dormant status and have gotten no feedback. Given there has been no
> development activity in years and there is no one actively working on the
> project
I started a discussion several days ago regarding moving Log4PHP to dormant
status and have gotten no feedback. Given there has been no development
activity in years and there is no one actively working on the project it seems
it should be moved to dormant status.
This vote will be open for
Most of the committers for Log4PHP have gone on to other things. The few that
are still participating in the Logging Services PMC have indicated that they
are not working on the project any more. As such, no one has been maintaining
the project for quite a while. The PMC has discussed moving
t;
> From: Christian Grobmeier
> Sent: Wednesday, October 30, 2019 7:45:08 AM
> To: dev@logging.apache.org
> Subject: Re: [LOG4PHP] Site Generation
>
> I would love if we could separate the logging pages from the release cycle.
> There was once
v2 docs.
Kate
From: Christian Grobmeier
Sent: Wednesday, October 30, 2019 7:45:08 AM
To: dev@logging.apache.org
Subject: Re: [LOG4PHP] Site Generation
I would love if we could separate the logging pages from the release cycle.
There was once a blocker using Phing
scusses how the logging services web site and the individual logging
> >> projects are built. I’ve heard rumblings that the ASF CMS is being or has
> >> been replaced or that you can at least use git but I haven’t investigated
> >> that. I can tell you I have a love/hate rela
This page mentions that the branch is typically asf-site.
https://www.apache.org/dev/project-site.html
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Ralph Goers
Sent: Wednesday, October 30, 2019 3:17:09 PM
To: dev@logging.apache.org
Subject: Re: [L
gt; documentation is created. For Java it makes more sense since it generates
>> some neat stuff automatically but I am not sure what added value it would
>> bring to a project like log4php.
>>>
>>> So as far as that goes, the only thing that matters is that the source
>&
ionship with how the Log4j
> documentation is created. For Java it makes more sense since it generates
> some neat stuff automatically but I am not sure what added value it would
> bring to a project like log4php.
> >
> > So as far as that goes, the only thing that matters is that
mentation is created. For Java it makes more sense since it generates
> some neat stuff automatically but I am not sure what added value it would
> bring to a project like log4php.
>
> So as far as that goes, the only thing that matters is that the source
> for the site is in
Hi
On Tue, Oct 29, 2019, at 22:31, Kate Gray wrote:
> Whoops, sent that to you, not the list.
>
> Is this what you're looking for?
>
> https://cwiki.apache.org/confluence/display/LOGGINGLOG4PHP/ReleaseProcedure
>
> It looks like the URL of the project has been change
ically but I am not sure what added value it would bring to a project
like log4php.
So as far as that goes, the only thing that matters is that the source for the
site is in source control - we could even request a GitHub project to host all
the logging subproject web sites if we want - and th
I've updated some of the source documents. It looks like it's pretty broken -
apigen, for example, isn't stable above PHP5.The Release Candidate is
really brittle, requiring specific commits of other libraries.
There's an issue, LOG4PHP-192, that mentions using phing
Whoops, sent that to you, not the list.
Is this what you're looking for?
https://cwiki.apache.org/confluence/display/LOGGINGLOG4PHP/ReleaseProcedure
It looks like the URL of the project has been changed from "logging-log4php" to
"LOGGINGLOG4PHP".
Kate
I think we once had a release guide, but I also think it was on a wiki which
was removed?
https://cwiki.apache.org/confluence/display/logging-log4php
Guess we have to renew it
--
Christian Grobmeier
grobme...@gmail.com
On Thu, Sep 12, 2019, at 17:48, Matt Sicker wrote:
> Do we hav
Hello Kate,
On Sun, Oct 27, 2019, at 06:46, Kate Gray wrote:
> As I said, I'd be glad to. I started working on getting log4php
> working properly for PHP 7, as PHP5 is end of life, and no longer
> updated.
I am one of the original developers of Log4php (at Apache). Unfortunate
ging.apache.org
> Subject: Re: [LOG4PHP] Abandoned? Contributing?
>
> Kate,
>
> I’ve gone ahead and merged the two PRs you submitted. If you wouldn’t mind,
> could you review some of the outstanding PRs for correctness? If they look
> good I would be happy to merge those a
I don’t mind at all.
Get Outlook for iOS<https://aka.ms/o0ukef>
From: Ralph Goers
Sent: Monday, October 28, 2019 3:48:38 PM
To: dev@logging.apache.org
Subject: Re: [LOG4PHP] Abandoned? Contributing?
Kate,
I’ve gone ahead and merged the two PRs you sub
it PRs to GitHub. It isn’t really a mirror. The ASF used to
> mirror the internal Git repos to GitHub but now GitHub and the ASF repos are
> co-equal. However, since most of us aren’t too familiar with Log4PHP please
> feel free to ping us when you need someone with commit privileges
You should submit PRs to GitHub. It isn’t really a mirror. The ASF used to
mirror the internal Git repos to GitHub but now GitHub and the ASF repos are
co-equal. However, since most of us aren’t too familiar with Log4PHP please
feel free to ping us when you need someone with commit privileges
As I said, I'd be glad to. I started working on getting log4php working
properly for PHP 7, as PHP5 is end of life, and no longer updated.
Where would the best place to submit code be? I've started with a pull request
on the GitHub mirror (which is what packagist seems to use).
Several of the logging services projects are in need of attention and need more
volunteers to help maintain them. Log4PHP is one of those.
Any help you can provide would be most welcome!
Ralph
> On Oct 26, 2019, at 2:36 PM, Kate Gray wrote:
>
> Hello,
>
> Has log4php
Hello,
Has log4php been abandoned?
Looking at the log4php site, I can see that there's a lot of outdated
information.
Installation suggests using the PEAR channel, but that was shut down:
https://logging.apache.org/log4php/install.html
http://apache-logging.6191.n7.nabble.com/NOTICE
Do we have a release guide for this component? I don't think a new
release has been done in a few years at least.
On Thu, 12 Sep 2019 at 03:23, Daniil Skomarovskyi <0xbad0c...@gmail.com> wrote:
>
> Hi guys! I've made a merge request to the log4php repository and it
Hi guys! I've made a merge request to the log4php repository and it's
merged already. Could someone update the package on
https://packagist.org/packages/apache/log4php, please!
://gitbox.apache.org/repos/asf.
Ralph
> On Nov 21, 2018, at 2:47 PM, Alexey Efimov wrote:
>
> Hi there,
>
> Composer can not find repo at
> https://git-wip-us.apache.org/repos/asf/logging-log4php.git
> Was it moved somewhere or something got broken?
> This page https://logging.a
Seems like several users were affected by this recent change. The new URL
just replaces the git-wip-us sub domain with gitbox. I’m not sure what we
need to update downstream here, though, as log4php hasn’t had any
development in quite some time.
On Wed, Nov 21, 2018 at 16:46, Alexey Efimov wrote
Hi there,
Composer can not find repo at
https://git-wip-us.apache.org/repos/asf/logging-log4php.git
Was it moved somewhere or something got broken?
This page https://logging.apache.org/log4php/source-repository.html still
refers to path above
Thanks,
Alexey
Hi,
On Thu, May 17, 2018, at 00:20, Rocska Ádám wrote:
> I have just recently joined, and I plan to do my first contributions on
> log4php.
Welcome!
> For my next iteration I would like to focus on the following :
> I'd like to have a full namespace coverage throughout the rep
Hi Everyone!
I have just recently joined, and I plan to do my first contributions on log4php.
For my next iteration I would like to focus on the following :
I'd like to have a full namespace coverage throughout the repo.
I'd like to do a small test namespace refactor, to open the oppor
s, just what I hope I explain now better.
Saludos,
Jose
-Mensaje original-
De: Dominik Psenner [mailto:dpsen...@gmail.com]
Enviado el: martes, 8 de agosto de 2017 14:45
Para: dev@logging.apache.org
Asunto: RE: [log4net][log4php] Xml Config file
There is at the moment only the idea of a com
appenders or other things, I'm not talking about
this, just what I hope I explain now better.
Saludos,
Jose
-Mensaje original-
De: Dominik Psenner [mailto:dpsen...@gmail.com]
Enviado el: martes, 8 de agosto de 2017 14:45
Para: dev@logging.apache.org
Asunto: RE: [log4net][log4php]
provide a logging framework that fits into the
environments where they run.
You could base your configuration files on a common configuration file and
generate one for log4net and one for log4php during the release or
deployment process. However i doubt the effort outweighs the benefits
because
t think it is the right way to do things.
Saludos,
Jose
-Mensaje original-
De: Dominik Psenner [mailto:dpsen...@gmail.com]
Enviado el: lunes, 7 de agosto de 2017 21:16
Para: dev@logging.apache.org
Asunto: Re: [log4net][log4php] Xml Config file
To me this sounds rather strange beca
To me this sounds rather strange because it sounds like a mix-up of
unrelated applications. Let me explain my reasoning..
Typically, log4net would run on an entirely different machine than where
log4php runs (i.e. apache2). At least it would not coexist within an
apache2 process since apache2
n 7 August 2017 at 07:59, Dominik Psenner wrote:
> You have an application that both runs log4net AND log4php in the same
> process?
>
> On 7 Aug 2017 12:51 p.m., "Domínguez Moraleja, Jose Luis" <
> jldomingue...@sice.com> wrote:
>
> > I'm working in
You have an application that both runs log4net AND log4php in the same
process?
On 7 Aug 2017 12:51 p.m., "Domínguez Moraleja, Jose Luis" <
jldomingue...@sice.com> wrote:
> I'm working in a project and we want to use this two libraries log4php and
> log4net.
I'm working in a project and we want to use this two libraries log4php and
log4net.
We want to use just one configuration file, is there any way to do it like
[
https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludvik Jerabek updated LOG4PHP-238:
---
Description:
The issue appear to only manifest itself when implementing class level logging
[
https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludvik Jerabek updated LOG4PHP-238:
---
Summary: Logging from (ppid) class destructor fails after forked child
processes exit
[
https://issues.apache.org/jira/browse/LOG4PHP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludvik Jerabek updated LOG4PHP-238:
---
Summary: Logging from class destructor fails when after forked child
processes exit
Ludvik Jerabek created LOG4PHP-238:
--
Summary: Logging from class destructor fails when from forked
child processes
Key: LOG4PHP-238
URL: https://issues.apache.org/jira/browse/LOG4PHP-238
Project
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Component/s: Code
> unable to install log4php via pear: unable to resolv hostn
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Environment: centos 7, php 5.6 via rh scl repo and php 5.6, 7.0 and 7.1
with
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Priority: Critical (was: Major)
> unable to install log4php via pear: unable
[
https://issues.apache.org/jira/browse/LOG4PHP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dietrich Streifert updated LOG4PHP-237:
---
Description:
When trying the discover part of pear for the pear.apache.org/log4php
Dietrich Streifert created LOG4PHP-237:
--
Summary: unable to install log4php via pear: unable to resolv
hostname pear.apache.org
Key: LOG4PHP-237
URL: https://issues.apache.org/jira/browse/LOG4PHP-237
[
https://issues.apache.org/jira/browse/LOG4PHP-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusuf Gündüz updated LOG4PHP-236:
-
Description:
Hello,
1. Is there any way to write the log with json format for using it on
[
https://issues.apache.org/jira/browse/LOG4PHP-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusuf Gündüz updated LOG4PHP-236:
-
Description:
Hello,
Is there any way to write the log to json format for using it on graylog
Yusuf Gündüz created LOG4PHP-236:
Summary: JSON formatted logs
Key: LOG4PHP-236
URL: https://issues.apache.org/jira/browse/LOG4PHP-236
Project: Log4php
Issue Type: New Feature
Affects
[
https://issues.apache.org/jira/browse/LOG4PHP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000514#comment-16000514
]
sharif Uddin commented on LOG4PHP-227:
--
I replaced line 62 of the file with
[
https://issues.apache.org/jira/browse/LOG4PHP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000505#comment-16000505
]
sharif Uddin commented on LOG4PHP-227:
--
any update on this issue as I am having
[
https://issues.apache.org/jira/browse/LOG4PHP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curtis Kelsey updated LOG4PHP-235:
--
Description:
When attempting to clone the package via composer server certificate
[
https://issues.apache.org/jira/browse/LOG4PHP-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curtis Kelsey updated LOG4PHP-235:
--
Description:
When attempting to clone the package via composer server certificate
Curtis Kelsey created LOG4PHP-235:
-
Summary: Server certificate verification fails via Git
Key: LOG4PHP-235
URL: https://issues.apache.org/jira/browse/LOG4PHP-235
Project: Log4php
Issue Type
64 matches
Mail list logo
