Ron, you had me worried for a minute. I thought you were doing something that
would affect what the release plugin does, not something in the web site.
Ralph
> On Dec 26, 2021, at 2:20 PM, Ron Grabowski
> wrote:
>
> I interpreted your comment as the branch name on the 2.17.0 site says
> 'log
Scott has been sort of maintaining Chainsaw on his own for years. I am sure he
would love new energy in the project.
I think isolating it from any logging framework implementation would be a good
thing.
Ralph
> On Dec 26, 2021, at 2:13 PM, Robert Middleton wrote:
>
> I've been looking into
Note that it is not the branch name that starts with "rel/", it is the tag
name.
Gary
On Sun, Dec 26, 2021, 16:21 Ron Grabowski
wrote:
> I interpreted your comment as the branch name on the 2.17.0 site says
> 'log4j-2.17.0' which doesn't exist, it should be 'rel/2.17.0'. I updated
> pom.xml in
I interpreted your comment as the branch name on the 2.17.0 site says
'log4j-2.17.0' which doesn't exist, it should be 'rel/2.17.0'. I updated
pom.xml in release-2.x to use the rel/x.y.z pattern in future deploys. When the
2.17.0 site is redeployed source-repository.html will be updated with th
The Log4j 1.x repo is now at https://github.com/apache/logging-log4j1. The
default branch is now “main”, a branch off the v1_2_17 tag.
Ralph
I've been looking into Chainsaw to remove Log4j1, since that is rather
obsolete at this point. Unfortunately, Chainsaw is closely tied to
Log4j1, as it seems that what happens is when it receives events from
a source, it sends the messages to a custom LoggerRepository with a
custom appender that w
On Sun, Dec 26, 2021 at 6:16 AM Volkan Yazıcı wrote:
> Many people get confused by the default branch of the repository on GitHub.
> I want to make it point to `release-2.x` rather than `master`. Objections?
>
+1
Gary
Please don’t forget to apply this to the master branch.
Ralph
> On Dec 26, 2021, at 6:31 AM, ggreg...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> ggregory pushed a commit to branch release-2.x
> in repository https://gitbox.apache.org/repos/asf
Please don’t forget to apply this to the master branch
Ralph
> On Dec 25, 2021, at 12:20 PM, cko...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> ckozak pushed a commit to branch release-2.x
> in repository https://gitbox.apache.org/repos/asf/log
Infra has a mailing list and a slack channel.
Ralph
> On Dec 26, 2021, at 6:00 AM, Carter Kozak wrote:
>
> I filed an infra ticket for this, but it hasn’t been picked up yet:
> https://issues.apache.org/jira/browse/INFRA-22641
> Might be worth emailing someone? Otherwise they may be busy with
I filed an infra ticket for this, but it hasn’t been picked up yet:
https://issues.apache.org/jira/browse/INFRA-22641
Might be worth emailing someone? Otherwise they may be busy with the holidays.
-ck
> On Dec 26, 2021, at 06:16, Volkan Yazıcı wrote:
>
> Many people get confused by the defaul
Am So., 26. Dez. 2021 um 12:16 Uhr schrieb Volkan Yazıcı :
> Many people get confused by the default branch of the repository on GitHub.
> I want to make it point to `release-2.x` rather than `master`. Objections?
While you're at that:
https://logging.apache.org/log4j/2.x/source-repository.html me
Many people get confused by the default branch of the repository on GitHub.
I want to make it point to `release-2.x` rather than `master`. Objections?
13 matches
Mail list logo