Fixing the rat report post-release is ok with me. There are differences to the last release:

These are fine by me because they are generated files:
  src/GeneratedAssemblyInfo.cs
  bin/mono/4.0/release/log4net.xml
  bin/mono/4.0/oldkey/log4net.xml
  bin/mono/4.0/debug/log4net.xml
  bin/mono/2.0/release/log4net.xml
  bin/mono/2.0/oldkey/log4net.xml
  bin/mono/2.0/debug/log4net.xml
  bin/mono/3.5/release/log4net.xml
  bin/mono/3.5/oldkey/log4net.xml
  bin/mono/3.5/debug/log4net.xml

These files however should be discussed:

  log4net.snk.readme
  tests/lib/prerequisites.txt

These two should contain a small license header.

On 2015-11-09 09:36, Stefan Bodewig wrote:
On 2015-11-09, Dominik Psenner wrote:

Good catch, Ralph. On past releases I used the RAT report to check if
there are differences and if there were differences I doublechecked if
they were OK or not. But somehow the "Project Reports" link has gone
missing:
https://logging.apache.org/log4net/rat-report.html
Ah, Maven 2.x -> 3.x and the site plugin, something I'd like to address
after the release (given the RAT report is probably just noise for most
of our users).

http://people.apache.org/~bodewig/log4net/rat-report.html

has been just created by running

$ mvn apache-rat:rat

in a checkout of the tag where I had built the Mono parts.  All files in
bin/ as well as src/GeneratedAssemblyInfo.cs have been generated during
the build process.

Stefan

Reply via email to