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 information. Instead, the changes are being documented in the release notes manually - see https://github.com/apache/logging-log4net/blob/rel/2.0.8/src/site/xdoc/release/release-notes.xml. This is a harder way to do it but it works I guess.
Log4j uses the changes.xml and the announcement plugin to generate the release notes. That uses a velocity template and automatically merges the changes report into it. We manually change the template a little bit for each release to cover the release highlights but everything else is automatically inserted. Ralph > On Aug 26, 2020, at 9:18 AM, Davyd McColl <dav...@gmail.com> wrote: > > 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 > text-search). > > I'll report back when I have something that works. > > -d > > On 2020/08/26 17:26:18, Davyd McColl <dav...@gmail.com> wrote: > Thanks Ralph, will give that all a go tonight! > -d > > On August 26, 2020 17:24:40 Ralph Goers <ralph.go...@dslextreme.com> 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/log4net > Once you have a site you are happy with the instructions on the link Matt > gave you will tell you how to update the public site. > But first you have to get the site build working again. > Ralph > On Aug 26, 2020, at 8:17 AM, Ralph Goers <ralph.go...@dslextreme.com> wrote: > 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 > no longer work. > Ralph > On Aug 26, 2020, at 8:06 AM, Matt Sicker <boa...@gmail.com> wrote: > I think these instructions are still up to date: > https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site > > [https://cwiki.apache.org/confluence/display/LOGGING/Managing+the+Logging+Services+Web+Site] > On Wed, 26 Aug 2020 at 10:02, Davyd McColl <dav...@gmail.com> wrote: > > > 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 <ralph.go...@dslextreme.com> wrote: > 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 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 > -- > Matt Sicker <boa...@gmail.com>
