Re: [LOG4PHP] Site Generation

I generally post the Log4j web site to my github.io account for review before publishing it live. That way everyone can see what it looks like. Ralph > On Oct 30, 2019, at 1:31 PM, Kate Gray wrote: > > If the UTF-8 issue isn’t fixed, I’ll fix it. > > I’m going to go ahead

Re: Log4Net Extensions for ASPNet Core

The codebase of your project could certainly be integrated into the apache log4net project or apache logging family. This would further lay the path to publish the project on nuget under the umbrella of Apache.Logging when a formal release of that project is made. Brian, are you interested in joini

Re: [LOG4PHP] Site Generation

If the UTF-8 issue isn’t fixed, I’ll fix it. I’m going to go ahead and use my GitHub fork to put together a demo site. If the project owners like it, I’ll put it in a PR. I’ll try to do something like symfony’s multi version documentation so that we can release a v3 without obliterating the v2

Re: [LOG4PHP] Site Generation

Some info: https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories If we use Pelican (similar to Jekyll), there's even automatic support for building it: https://github.com/apache/infrastructure-website The gist is to commit your built site to the asf-site branch

Re: [LOG4PHP] Site Generation

This page mentions that the branch is typically asf-site. https://www.apache.org/dev/project-site.html Get Outlook for iOS From: Ralph Goers Sent: Wednesday, October 30, 2019 3:17:09 PM To: dev@logging.apache.org Subject: Re: [LOG4PHP] Si

Re: [LOG4PHP] Site Generation

Do you have a link? I just went through a lot of pain to upgrade the Log4j site to use the latest version of the site plugin. Unfortunately, our custom stuff didn’t work and I had to switch to the maven fluido plugin, which is good but not quite as nice. But at least now markdown works better.

Re: Log4Net Extensions for ASPNet Core

I'm not even sure how log4net is published on nuget, though any projects published under Apache there would have to be Apache projects. Perhaps another organization for extras or something would be useful here? There used to be something like that for log4j at least. On Wed, 30 Oct 2019 at 10:59,

Re: [LOG4PHP] Site Generation

You can use a specially named branch in git to be an automatically published site (similar to GitHub Pages, but ASF-specific). There’s a Jenkins node label for running jobs to deploy the branch’s contents to the site. On Wed, Oct 30, 2019 at 07:45, Christian Grobmeier wrote: > I would love if we

Log4Net Extensions for ASPNet Core

I have written a small project that hooks log4net into asp net core architecture and am looking to publish the package to nuget under the apache foundation. Brian Sent from Outlook

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, I think it had something to do with not supporting UTF-8 correclty. Most likely this is gone by now and I would be fine to move on. -- Christian Grobmeier grobme...@gmail.com

Re: log4php update

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 changed from > "logging-log4php"