I’m in with the partent pom right now….can work on getting that sorted…plus I
need to to get our release plugin working with the latest version of maven.
-Rob
> On Jan 22, 2022, at 5:42 PM, Matt Sicker wrote:
>
> Alright, digging through the parent parent parent pom, it looks like the
>
Alright, digging through the parent parent parent pom, it looks like the Apache
parent pom has a release date from 2020 which is what ended up getting used by
the javadocs. This was fixed in that parent pom version 24, so we could
probably use an updated version of the commons parent pom as
The copyright year is derived from POM properties or can be hard coded.
Trying to have a reproducible build can further muck things up where you
end up with 1969 as then end year as I recently fixed in Log4j. AFK but
there is a property called output build timestamp or something like that
that I
Looks like some of the non-blockers are things I didn’t notice before (like the
user’s guide). I suppose I assumed that the site build automatically added
links to the new release, though that only seems to be for the download page. I
can update this in git (though it might require a second
Le sam. 22 janv. 2022 à 15:30, Avijit Basak a écrit :
>
> Hi
>
> >Please be sure to use my latest (forced) update.
> >[I removed the many duplicate commits I had introduced by mistake.]
>
> --Is the change only in commons-math-examples/pom.xml file? Please confirm.
No, there can be other
Hi
>Please be sure to use my latest (forced) update.
>[I removed the many duplicate commits I had introduced by mistake.]
--Is the change only in commons-math-examples/pom.xml file? Please confirm.
My changes are creating conflict after this push. I shall create a new PR.
Thanks & Regards
Thank you for cutting the RC! :-)
Maybe blocker:
The Javadoc end copyright year is 2020 instead of 2022.
Not blockers:
The git tag name does not match the instructions below so the git clone
command fails (upper case instructions, lower case in actuality).
New Blake3 class has a FindBugs
