Our Commons plugin takes care of updating the NOTICE file when a release is
created, so no need to do anything for now IMO.
Gary
On Sun, Jan 10, 2021, 12:23 Matt Sicker wrote:
> The fact that it's in a single file rather than in the copyright
> header of every file as is typically done already
AIUI, the date should only be updated if there has been a substantive
change to the software.
So we don't have to go and change all the NOTICE files.
However, before release, we should certainly check the date.
On Sun, 10 Jan 2021 at 17:23, Matt Sicker wrote:
>
> The fact that it's in a single
I'm going to vote -1 on RC1 as I forgot to sign the Windows binaries.
I'll fix the issues Bruno notes below and then roll an RC2.
Mark
On 08/01/2021 03:42, Bruno P. Kinoshita wrote:
> [x] +1 Release these artifacts
>
> NB: the NOTICE file needs the yearly update, from 2020 to 2021. Not a blo
The fact that it's in a single file rather than in the copyright
header of every file as is typically done already reduces the number
of things to update at least. :)
Maybe there's a thing in the commons maven plugin?
On Sun, 10 Jan 2021 at 11:01, Xeno Amess wrote:
>
> In nearly all repos in our
In nearly all repos in our commons, there be a file named NOTICE.txt, and
content be:
Apache Commons Lang
Copyright 2001-2020 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (https://www.apache.org/).
Since it be 2021 now, should we chang
Hello Gary,
thanks for your advice. All test mentioned run fine with commons-io 2.5,
addressing it here seems right.
There are new issues with the current 2.9.0-snapshot. Previously with 2.8.0 it
was
https://github.com/wildfly/wildfly-core/blob/ce3b0e1b66ac39c1832dfea1735069e17bbc4fe1/testsuit
