All the NuGet emails are forwarded to the Logging PMC. We are getting requests
to see the changes between 2.0.8 and 2.0.9. In the future I would suggest we
not push to NuGet until the web site is updated. To avoid this.
Ralph
Davyd, Can you update the web site? It still says Log4Net is dormant and does
not include any info about 2.0.0. The PMC is continuing to get queries since
there is no public info about the release.
Ralph
> On Aug 24, 2020, at 3:31 PM, Ralph Goers wrote:
>
> All the NuGet emails are forwarde
Ralph, I'm happy to -- but I have no idea how to. Even a pointer at a document
I can read on how would be greatly appreciated (ie how to get content to the
website)
-d
On 2020/08/26 16:54:46, Ralph Goers wrote:
Davyd, Can you update the web site? It still says Log4Net is dormant and does
not
I think these instructions are still up to date:
https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site
On Wed, 26 Aug 2020 at 10:02, Davyd McColl wrote:
>
> Ralph, I'm happy to -- but I have no idea how to. Even a pointer at a
> document I can read on how wo
Thanks Matt, I'll give that a go tonight (:
-d
On 2020/08/26 17:07:00, Matt Sicker wrote:
I think these instructions are still up to date:
https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site
On Wed, 26 Aug 2020 at 10:02, Davyd McColl wrote:
>
> Ralph, I'm
Actually, I can handle the main web site. I just need the Log4Net site updated.
From what I can tell it uses the Maven site plugin. That requires files in the
src/site and src/changes directory that were present in the 2.0.8 release but
seem to have been moved to src/Log4Net/site where they will
Building the site should just require running
mvn site
in the home directory of the log4net project. To get it somewhere you can view
you can then do
mvn site:stage -DstagingDirectory=$HOME/log4net
Once you have a site you are happy with the instructions on the link Matt gave
you will tell yo
Thanks Ralph, will give that all a go tonight!
-d
On August 26, 2020 17:24:40 Ralph Goers wrote:
Building the site should just require running
mvn site
in the home directory of the log4net project. To get it somewhere you can
view you can then do
mvn site:stage -DstagingDirectory=$HOME/
update: I have the site building with maven, but a _lot_ of the links are
broken (target html file is missing), so I'm going to have to hunt those down.
I'm also not sure how a changelog ends up in the site, since the changes folder
doesn't seem to e referenced (that I could find via a quick tex
I've raised a PR in the interim: all I've done is move the site assets back
where they belong (I inadvertently moved them out when refactoring for build!).
I have a lot to learn to understand what maven is doing, so right now, I'm not
very clued up as to why a lot of links in the generated outpu
Normally, src/changes/changes.xml should have the list of changes for each
release. The Maven site plugin runs the changes plugin -
https://maven.apache.org/plugins/maven-changes-plugin/ - would normally process
that. But it appears Log4net isn’t using that as it doesn’t contain any useful
info
If you have moved them back I can take a look this evening when I have some
time.
Ralph
> On Aug 26, 2020, at 10:22 AM, Davyd McColl wrote:
>
> I've raised a PR in the interim: all I've done is move the site assets back
> where they belong (I inadvertently moved them out when refactoring for
Thanks Ralph
I've figured out part of the problem: I updated the .gitignore as part of the
build / maintenance update & the default gitignore rule for vs projects
excludes folders called 'release', which left out release docs from the site.
I've copied in from the develop branch and updated the
Ralph, I've pushed to that PR with updated release notes based on what I could
grok from prior commits, basically:
- update to support netstandard2.0 & project restructuring
- address LOG4NET-559 (adds null checks to prevent some reported issues with
custom appenders)
- address LOG4NET-563, whic
14 matches
Mail list logo
