> On May 25, 2019, at 3:15 PM, Matt Sicker wrote:
>
> Hi, I've gone ahead and approved it after review. Since I'm not active
> in beanutils, I'd prefer someone else to either merge it or add an
> approval review first. My company has also been moving toward
> eliminating vulnerable versions of
Hi, I've gone ahead and approved it after review. Since I'm not active
in beanutils, I'd prefer someone else to either merge it or add an
approval review first. My company has also been moving toward
eliminating vulnerable versions of dependencies, and we use beanutils
(1.9.x currently) in some lim
On Sat, 25 May 2019 at 12:25, Maxim Solodovnik wrote:
>
> This is caused by different versions of maven-project-info-reports-plugin
>
> https://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice
>
I see, thanks for the info.
==
That's a big nuisance.
We cannot re
This is caused by different versions of maven-project-info-reports-plugin
https://maven.apache.org/plugins/maven-project-info-reports-plugin/#Incompatibility_Notice
On Sat, 25 May 2019 at 17:24, sebb wrote:
> Why do some components use:
>
> http://commons.apache.org/proper/commons-lang/scm.ht
Why do some components use:
http://commons.apache.org/proper/commons-lang/scm.html
and some use
http://commons.apache.org/proper/commons-math/source-repository.html
They have the same content, so why the different URLs?
Should we standardise on one (and add redirects for the other?)
Are there a
Hi.
Le ven. 24 mai 2019 à 06:01, Eitan Adler a écrit :
>
> (please make sure to CC me on replies)
>
> +1 on this. One thing I'd like for us to avoid a mess of different junit
> versions making it difficult to know which runner will be executing the
> class. It would be great if we did a complete
