I typically will test the Log4J build during the maven release vote. That is
the time to see if there are problems. I don't upgrade the maven version on the
machine that performs the releases very often.
Ralph
> On Apr 9, 2017, at 8:20 AM, Gary Gregory wrote:
>
> I was thinking of just using
I was thinking of just using 3.5.0.
Gary
On Apr 9, 2017 6:48 AM, "Apache" wrote:
> Why? There is no reason our build process has to support every maven
> release.
>
> Sent from my iPad
>
> On Apr 8, 2017, at 5:44 PM, Matt Sicker wrote:
>
> Now that Maven 3.5.0 is out, whenever Infra adds it to
Why? There is no reason our build process has to support every maven release.
Sent from my iPad
> On Apr 8, 2017, at 5:44 PM, Matt Sicker wrote:
>
> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it make
> sense to switch to it there? I know in theory everything seems t
Sure, why not? Let's eat our own Apache dog food. Fresh too!
Gary
On Apr 8, 2017 5:44 PM, "Matt Sicker" wrote:
> Now that Maven 3.5.0 is out, whenever Infra adds it to Jenkins, would it
> make sense to switch to it there? I know in theory everything seems to work
> with any version of Maven 3.x
